View AM29BDS640HD9VMI_8305467.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

publication number 27024 revision b amendment 3 issue date may 10, 2006 am29bds128h/am29bds640h data sheet retired product (am29bds40h only) the am29bds640h has been retired and is not recommended for designs. for new designs, s29ws064k supersedes am29bds640h. please refer to the s29ws-k family data sheet for speci- fications and ordering information. the am29bds128h is available and is not affected by this revi- sion. the following document contains inform ation on spansion memory products. continuity of specifications there is no change to this data sheet as a result of offering the device as a spansion product. any changes that have been made are the result of no rmal data sheet improvement and are noted in the document revision summary. future routine revision s will occur when appropriate, and changes will be noted in a revision summary. continuity of ordering part numbers spansion continues to support the am29bds640h pa rt numbers. to order these products, please use only the ordering part numb ers listed in this document. for more information please contact your local sales office for additi onal information about spansion memory solutions. (
this page left intentionally blank.
data sheet publication# 27024 rev: b amendment: 3 issue date: may 10, 2006 am29bds128h/am29bds640h 128 or 64 megabit (8 m or 4 m x 16-bit) cmos 1.8 volt-only simultaneous re ad/write, burst mode flash memory distinctive characteristics architectural advantages single 1.8 volt read, program and erase (1.65 to 1.95 volt) manufactured on 0.13 m process technology versatileio? (v io ) feature ? device generates data output voltages and tolerates data input voltages as determined by the voltage on the v io pin ? 1.8v compatible i/o signals simultaneous read/write operation ? data can be continuously read from one bank while executing erase/program functions in other bank ? zero latency between read and write operations ? four bank architecture: 128 mb has 16/48/48/16 mbit banks 64 mb has 8/24/24/8 mbit banks programable burst interface ? 2 modes of burst read operation ? linear burst: 8, 16, and 32 words with wrap-around ? continuous sequential burst secsi tm (secured silicon) sector region ? up to 128 words accessible through a command sequence ? up to 64 factory-locked words ? up to 64 customer-lockable words sector architecture ? banks a and d each contain both 4 kword sectors and 32 kword sectors; banks b and c contain ninety-six 32 kword sectors ? sixteen 4 kword boot sectors half of the boot sectors are at the top of the address range; half are at the bottom of address range minimum 1 million erase cycle guarantee per sector 20-year data retention at 125c ? reliable operation for the life of the system 80-ball fbga package (128 mb) or 64-ball fbga (64 mb) package performance charcteristics read access times at 75/66/54 mhz (c l =30 pf) ? burst access times of 9.3/11/13.5 ns at industrial temperature range ? synchronous latency of 49/56/69 ns ? asynchronous random access times of 45/50/55 ns power dissipation (typical values, c l = 30 pf) ? burst mode read: 10 ma ? simultaneous operation: 25 ma ? program/erase: 15 ma ? standby mode: 0.2 a hardware features handshaking feature ? provides host system with minimum possible latency by monitoring rdy ? reduced wait-state handshaking option further reduces initial access cycles required for burst accesses beginning on even addresses hardware reset input (reset#) ? hardware method to reset the device for reading array data wp# input ? write protect (wp#) function allows protection of the four highest and four lowest 4 kword boot sectors, regardless of sector protect status persistent sector protection ? a command sector protection method to lock combinations of individual sectors and sector gr oups to prevent program or erase operations within that sector ? sectors can be locked and unlocked in-system at v cc level password sector protection ? a sophisticated sector protection method to lock combinations of individual se ctors and sector groups to prevent program or erase operati ons within that sector using a user-defined 64-bit password acc input: acceleration function reduces programming time; all sectors locked when acc = v il cmos compatible inputs, cmos compatible outputs low v cc write inhibit software features supports common flash memory interface (cfi) software command set compatible with jedec 42.4 standards ? backwards compatible with am29f and am29lv families data# polling and toggle bits ? provides a software method of detecting program and erase operation completion erase suspend/resume ? suspends an erase operation to read data from, or program data to, a sector that is not being erased, then resumes the erase operation unlock bypass program command ? reduces overall programming time when issuing multiple program command sequences burst suspend/resume ? suspends a burst operation to allow system use of the address and data bus, than resumes the burst at the previous state the am29bds640h has been retired and is not recommended for desi gns. for new designs, s29ws 064k supersedes am29bds640h. please refer to the s29ws-k family data sheet for specifications and ordering informati on. the am29bds128h is available and is not affected by this revision.
2 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet general description the am29bds128h/am29bds640h is a 128 or 64 mbit, 1.8 volt-only, simultaneous read/write, burst mode flash mem- ory device, organized as 8,388,608 or 4,194,304 words of 16 bits each. this device uses a single v cc of 1.65 to 1.95 v to read, program, and erase the memory array. a 12.0-volt v hh on acc may be used for faster program performance if de- sired. the device can also be programmed in standard eprom programmers. at 75 mhz, the device provides a burst access of 9.3 ns at 30 pf with a latency of 49 ns at 30 pf. at 66 mhz, the device provides a burst access of 11 ns at 30 pf with a latency of 56 ns at 30 pf. at 54 mhz, the device provides a burst ac- cess of 13.5 ns at 30 pf with a latency of 69ns at 30 pf. the device operates within the industrial temperature range of -40c to +85c. the device is offered in fbga packages. the simultaneous read/write architecture provides simul- taneous operation by dividing the memory space into four banks. the device can improv e overall system performance by allowing a host system to program or erase in one bank, then immediately and simult aneously read from another bank, with zero latency. this releases the system from wait- ing for the completion of program or erase operations. the device is divided as shown in the following table: the versatileio? (v io ) control allows the host system to set the voltage levels that the device generates at its data out- puts and the voltages tolerated at its data inputs to the same voltage level that is asserted on the v io pin. the device uses chip enable (ce#), write enable (we#), address valid (avd#) and output enable (oe#) to control asynchronous read and write operations. for burst opera- tions, the device additionally requires ready (rdy), and clock (clk). this implementation allows easy interface with minimal glue logic to a wide range of microprocessors/micro- controllers for high performance read operations. the burst read mode feature gives system designers flexibil- ity in the interface to the device. the user can preset the burst length and wrap through the same memory space, or read the flash array in continuous mode. the clock polarity feature provides system designers a choice of active clock edges, either rising or falling. the ac- tive clock edge initiates burst accesses and determines when data will be output. the device is entirely command set compatible with the jedec 42.4 single-power -supply flash standard . com- mands are written to the co mmand register using standard microprocessor write timing. register contents serve as in- puts to an internal state-machine that controls the erase and programming circuitry. write cycles also internally latch ad- dresses and data needed for the programming and erase operations. reading data out of the device is similar to read- ing from other flash or eprom devices. the erase suspend/erase resume feature enables the user to put erase on hold for any period of time to read data from, or program data to, any sector that is not selected for erasure. true background erase can thus be achieved. if a read is needed from the secsi sector area (one time pro- gram area) after an erase su spend, then the user must use the proper command sequence to enter and exit this region. the hardware reset# pin terminates any operation in progress and resets the internal state machine to reading array data. the reset# pin may be tied to the system reset circuitry. a system reset would thus also rese t the device, enabling the system mi croprocessor to re ad boot-up firm- ware from the flash memory device. the host system can detect whether a program or erase op- eration is complete by using the device status bit dq7 (data# polling) and dq6/dq2 (t oggle bits). after a program or erase cycle has been completed, the device automatically returns to reading array data. the sector erase architecture allows memory sectors to be erased and reprogrammed witho ut affecting the data con- tents of other sectors. the device is fully erased when shipped from the factory. hardware data protection measures include a low v cc de- tector that automatically inhi bits write operations during power transitions. the device also offers two types of data protection at the sector level. when at v il , wp# locks the four highest and four lowest boot sectors. the device offers two power-saving features. when ad- dresses have been stable for a specified amount of time, the device enters the automatic sleep mode . the system can also place the device into the standby mode . power con- sumption is greatly reduced in both modes. amd flash technology combines years of flash memory manufacturing experience to produce the highest levels of quality, reliability and cost effectiveness. the device electri- cally erases all bits within a sector simultaneously via fowler-nordheim tunnelling. the data is programmed using hot electron injection. bank quantity size 128 mb 64 mb a 8 8 4 kwords 31 15 32 kwords b 96 48 32 kwords c 96 48 32 kwords d 31 15 32 kwords 8 8 4 kwords
may 10, 2006 27024b3 am29bds128h/am29bds640h 3 data sheet table of contents product selector guide . . . . . . . . . . . . . . . . . . . . . 5 block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 block diagram of simultaneous operation circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 connection diagram . . . . . . . . . . . . . . . . . . . . . . . . 7 special handling instructions for fbga package .................... 8 input/output descriptions . . . . . . . . . . . . . . . . . . . 9 logic symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 ordering information . . . . . . . . . . . . . . . . . . . . . . 10 device bus operations . . . . . . . . . . . . . . . . . . . . . 11 table 1. device bus operations ....................................................11 requirements for asynchronous read operation (non-burst) ............................................................ 11 requirements for synchronous (burst) read operation ........ 11 8-, 16-, and 32-word linear burst with wrap around ............ 12 table 2. burst address groups .......................................................12 burst suspend/resume .......................................................... 12 configuration register ............................................................ 13 reduced wait-state handshaking option .............................. 13 simultaneous read/write operations with zero latency ....... 13 writing commands/command sequences ............................ 13 accelerated program operation ............................................. 14 autoselect mode ..................................................................... 14 table 3. autoselect codes (high voltage method) ........................15 table 4. am29bds128h boot sector/sector block addresses for pro- tection/unprotection ........................................................................16 table 5. am29bds640h boot sector/sector block addresses for pro- tection/unprotection ........................................................................17 sector/sector block protection and unprotection .................. 17 sector protection .................................................................... 17 selecting a sector protection mode ....................................... 17 persistent sector protection ................................................... 18 persistent protection bit (ppb) ............................................... 18 persistent protection bit lock (ppb lock) ............................. 18 dynamic protection bit (dyb) ................................................ 18 table 6. sector protection schemes ...............................................19 persistent sector protection mode locking bit ...................... 19 password protection mode ..................................................... 19 password and password mode locking bit ........................... 20 64-bit password ...................................................................... 20 persistent protection bit lock ................................................. 20 high voltage sector protection .............................................. 20 standby mode ........................................................................ 20 automatic sleep mode ........................................................... 21 reset#: hardware reset input ............................................. 21 output disable mode .............................................................. 21 figure 1. temporary sector unprotect operation........................... 21 figure 2. in-system sector protection/ sector unprotection algorithms ...................................................... 22 secsi? (secured silicon) sector flash memory region ............................................................ 23 factory-locked area (64 words) ............................................ 23 table 7. secsi tm sector addresses ...............................................23 customer-lockable area (64 words) ...................................... 23 secsi sector protection bits ................................................... 23 hardware data protection ...................................................... 23 write protect (wp#) ................................................................ 24 low v cc write inhibit .............................................................. 24 write pulse ?glitch? protection ................................................ 24 logical inhibit .......................................................................... 24 power-up write inhibit ............................................................ 24 table 8. cfi query identification string ......................................... 24 table 9. system interface string .................................................... 25 table 10. device geometry definition ........................................... 25 table 11. primary vendor-specific extended query ..................... 26 table 12. am29bds128h sector address table .......................... 27 table 13. am29bds640h sector address table .......................... 31 command definitions . . . . . . . . . . . . . . . . . . . . . 33 reading array data ................................................................ 33 set configuration register command sequence ................... 33 figure 3. synchronous/asynchronous state diagram ................... 33 read mode setting ................................................................. 33 programmable wait state configuration ................................ 33 table 14. programmable wait state settings ................................ 34 reduced wait-state handshaking option ............................... 34 table 15. wait states for reduced wait-state handshaking ........ 34 standard handshaking option ................................................ 35 table 16. wait states for standard handshaking .......................... 35 read mode configuration ....................................................... 35 table 17. read mode settings ....................................................... 35 burst active clock edge configuration ................................... 35 rdy configuration .................................................................. 35 table 18. configuration register ................................................... 36 reset command ..................................................................... 36 autoselect command sequence ............................................ 36 table 19. autoselect data .............................................................. 37 enter secsi? sector/exit secsi sector command sequence .............................................................. 37 program command sequence ............................................... 37 unlock bypass command sequence ..................................... 37 figure 4. program operation ......................................................... 38 chip erase command sequence ........................................... 38 sector erase command sequence ........................................ 38 erase suspend/erase resume commands ........................... 39 figure 5. erase operation.............................................................. 40 password program command ................................................ 40 password verify command .................................................... 40 password protection mode locking bit program command .. 40 persistent sector protection mode locking bit program com- mand ....................................................................................... 40 secsi sector protection bit program command .................... 41 ppb lock bit set command ................................................... 41 dyb write command ............................................................. 41 password unlock command .................................................. 41 figure 6. ppb program algorithm.................................................. 42 ppb program command ........................................................ 43 all ppb erase command ........................................................ 43 figure 7. ppb erase algorithm ...................................................... 44 dyb write command ............................................................. 45 ppb status command ............................................................ 45 ppb lock bit status command .............................................. 45 dyb status command ............................................................ 45 command definitions ............................................................. 46 table 20. memory array command definitions ............................ 46 table 21. sector protection command definitions ....................... 47
4 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet write operation status . . . . . . . . . . . . . . . . . . . . . 48 dq7: data# polling ................................................................. 48 figure 8. data# polling algorithm ................................................... 48 dq6: toggle bit i .................................................................... 49 figure 9. toggle bit algorithm......................................................... 50 dq2: toggle bit ii ................................................................... 50 table 22. dq6 and dq2 indications ...............................................51 reading toggle bits dq6/dq2 .............................................. 51 dq5: exceeded timing limits ................................................ 51 dq3: sector erase timer ....................................................... 51 table 23. write operation status ....................................................52 absolute maximum ratings . . . . . . . . . . . . . . . . . 53 figure 10. maximum negative overshoot waveform ..................... 53 figure 11. maximum positive overshoot waveform....................... 53 operating ranges . . . . . . . . . . . . . . . . . . . . . . . . 53 dc characteristics . . . . . . . . . . . . . . . . . . . . . . . . 54 cmos compatible . . . . . . . . . . . . . . . . . . . . . . . . . 54 test conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 figure 12. test setup...................................................................... 55 table 24. test specifications ..........................................................55 key to switching waveforms . . . . . . . . . . . . . . . 55 switching waveforms . . . . . . . . . . . . . . . . . . . . . 55 figure 13. input waveforms and measurement levels .................. 55 ac characteristics . . . . . . . . . . . . . . . . . . . . . . . . 56 v cc power-up ......................................................................... 56 figure 14. v cc power-up diagram ................................................. 56 clk characterization ............................................................. 56 figure 15. clk characterization..................................................... 56 synchronous/burst read ....................................................... 57 figure 16. clk synchronous burst mode read (rising active clk) ... .........................................................................................................58 figure 17. clk synchronous burst mode read (falling active clock) .........................................................................................................58 figure 18. synchronous burst mode read..................................... 59 figure 19. 8-word linear burst with wrap around .......................... 59 figure 20. linear burst with rdy set one cycle before data ....... 60 figure 21. reduced wait-state handshake burst suspend/resume at an even address............................................................................. 61 figure 22. reduced wait-state handshake burst suspend/resume at an odd address .............................................................................. 61 figure 23. reduced wait-state handshake burst suspend/resume at address 3eh (or offset from 3eh)................................................... 62 figure 24. reduced wait-state handshake burst suspend/resume at address 3fh (or offset from 3fh by a multiple of 64) ..................... 62 figure 25. standard handshake burst suspend prior to initial access .........................................................................................................63 figure 26. standard handshake burst suspend at or after initial ac- cess................................................................................................ 63 figure 27. standard handshake burst suspend at address 3fh (start- ing address 3dh or earlier)............................................................ 64 figure 28. standard handshake burst suspend at address 3eh/3fh (without a valid initial access)....................................................... 64 figure 29. standard handshake burst suspend at address 3eh/3fh (with 1 access clk)....................................................................... 65 figure 30. read cycle for continuous suspend............................ 65 asynchronous mode read .................................................... 66 ac characteristics . . . . . . . . . . . . . . . . . . . . . . . . 67 figure 31. asynchronous mode read with latched addresses .... 67 figure 32. asynchronous mode read............................................ 67 figure 33. reset timings ............................................................... 68 erase/program operations ..................................................... 69 figure 34. asynchronous program operation timings: avd# latched addresses ...................................................................................... 70 figure 35. asynchronous program operation timings: we# latched addresses ...................................................................................... 71 figure 36. synchronous program operation timings: we# latched addresses ...................................................................................... 72 figure 37. synchronous program operation timings: clk latched addresses ...................................................................................... 73 figure 38. chip/sector erase command sequence ...................... 74 figure 39. accelerated programming timing................................. 75 figure 40. data# polling timings (during embedded algorithm) .. 76 figure 41. toggle bit timings (during embedded algorithm)........ 76 figure 42. synchronous data polling timings/toggle bit timings 77 figure 43. dq2 vs. dq6................................................................. 77 temporary sector unprotect .................................................. 78 figure 44. temporary sector unprotect timing diagram .............. 78 figure 45. sector/sector block protect and unprotect timing diagram ............................................................. 79 figure 46. latency with boundary crossing .................................. 80 figure 47. latency with boundary crossing into program/erase bank ............................................................... 81 figure 48. example of wait states insertion.................................. 82 figure 49. back-to-back read/write cycle timings ...................... 83 erase and programming performance . . . . . . . 84 bga ball capacitance . . . . . . . . . . . . . . . . . . . . . 84 data retention. . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 physical dimensions . . . . . . . . . . . . . . . . . . . . . . 85 vbb080?80-ball fine-pitch ball grid array (bga) 11.5 x 9 mm package ........................................................................ 85 vbd064?64-ball fine-pitch ball grid array (bga) 9 x 8 mm package ........................................................................ 86 revision summary . . . . . . . . . . . . . . . . . . . . . . . . 87
may 10, 2006 27024b3 am29bds128h/am29bds640h 5 data sheet product selector guide note: speed options ending in ?8? indicate the ?reduced wait-state handshaking? option, which speeds initial synchronous accesses for even addresses. speed options ending in ?9? in dicate the ?standard handshaking? option. see the ac characteristics section of this da ta sheet for full specifications. block diagram note: a max = a22 (128 mb) or a21 (64 mb) part number am29bds128h/am29bds640h burst frequency 66 mhz 54 mhz speed option v cc , v io = 1.65 ? 1.95 v e8, e9 d8, d9 max initial synchronous access time, ns (t iacc ) reduced wait-state handshaking; even address 56 69 max initial synchronous access time, ns (t iacc ) reduced wait-state handshaking; od d address; or standard handshaking 71 87.5 max burst access time, ns (t bacc ) 11 13.5 max asynchronous access time, ns (t acc ) 50 55 max ce# access time, ns (t ce ) max oe# access time, ns (t oe ) 11 13.5 input/output buffers x-decoder y-decoder chip enable output enable logic erase voltage generator pgm voltage generator timer v cc detector state control command register v cc v ss v io we# reset# wp# acc ce# oe# dq15 ? dq0 data latch y-gating cell matrix address latch amax?a0 rdy buffer rdy burst state control burst address counter avd# clk
6 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet block diagram of simultaneous operation circuit v ss v cc v io bank b address reset# acc we# ce# avd# rdy dq15?dq0 wp# state control & command register bank b x-decoder y-decoder latches and control logic bank a x-decoder y-decoder latches and control logic dq15?dq0 dq15?dq0 dq15?dq0 dq15?dq0 dq15?dq0 bank c y-decoder x-decoder latches and control logic bank d y-decoder x-decoder latches and control logic oe# status control amax?a0 amax?a0 bank c address bank d address bank a address amax?a0 amax ?a0 amax ?a0
may 10, 2006 27024b3 am29bds128h/am29bds640h 7 data sheet connection diagram c2 d2 e2 f2 g2 h2 j2 k2 c3 d3 e3 f3 g3 h3 j3 k3 c4 d4 e4 f4 g4 h4 j4 k4 c5 d5 e5 f5 g5 h5 j5 k5 c6 d6 e6 f6 g6 h6 j6 k6 c7 d7 a7 b7 a8 b8 a1 b1 a2 e7 f7 g7 h7 j7 k7 l7 l8 m7 m8 l1 l2 m1 m2 nc nc nc b2 nc nc nc nc nc nc nc nc nc nc nc nc nc dq15 v ss nc a16 a15 a14 a12 a13 c8 d8 e8 f8 g8 h8 j8 k8 nc nc nc v ss v io nc a22 nc dq13 dq6 dq14 dq7 a11 a10 a8 a9 v cc dq4 dq12 dq5 a19 a21 reset# we# dq11 dq3 dq10 dq2 a20 a18 acc rdy dq9 dq1 dq8 dq0 a5 a6 a17 a7 oe# v ss ce# a0 a1 a2 a4 a3 c1 d1 e1 f1 g1 h1 j1 k1 v ss nc v io avd# wp# clk v cc nc 80-ball fine-pitch ball grid array top view, balls facing down (am29bds128h only)
8 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet special handling instructions for fbga package special handling is required for flash memory products in fbga packages. flash memory devices in fbga packages may be damaged if exposed to ultrasonic cleaning methods. the package and/or data integrity may be compro- mised if the package body is exposed to temperatures above 150c for prolonged periods of time. a2 b2 c2 d2 e2 f2 g2 h2 a3 b3 c3 d3 e3 f3 g3 h3 a4 b4 c4 d4 e4 f4 g4 h4 a5 b5 c5 d5 e5 f5 g5 h5 a6 b6 c6 d6 e6 f6 g6 h6 a7 b7 c7 d7 e7 f7 g7 h7 dq15 v ss nc a16 a15 a14 a12 a13 a8 b8 c8 d8 e8 f8 g8 h8 nc nc nc v ss v io nc nc nc dq13 dq6 dq14 dq7 a11 a10 a8 a9 v cc dq4 dq12 dq5 a19 a21 reset# we# dq11 dq3 dq10 dq2 a20 a18 acc rdy dq9 dq1 dq8 dq0 a5 a6 a17 a7 oe# v ss ce# a0 a1 a2 a4 a3 a1 b1 c1 d1 e1 f1 g1 h1 v ss nc v io avd# wp# clk v cc nc 64-ball fine-pitch ball grid array top view, balls facing down (am29bds640h only)
may 10, 2006 27024b3 am29bds128h/am29bds640h 9 data sheet input/output descriptions amax?a0 = address inputs amax = a22 (128 mb) or a21 (64 mb) dq15?dq0 = data input/output ce# = chip enable input. asynchronous relative to clk for the burst mode. oe# = output enable input. asynchronous relative to clk for the burst mode. we# = write enable input. v cc = device power supply (1.65 ? 1.95 v). v io = input & output buffer power supply (1.65 ? 1.95 v). v ss =ground nc = no connect; not connected internally rdy = ready output; in synchronous mode, indicates the status of the burst read. low = data invalid. high = data valid. in asynchronous mode, indicates the status of the internal program and erase function. low = program/erase in progress. high impedance = program/erase completed. clk = clk is not requir ed in asynchronous mode. in burst mode, after the initial word is output, subsequent active edges of clk increment the internal address counter. avd# = address valid input. indicates to device that the valid address is present on the address inputs (amax?a0). low = for asynchronous mode, indicates valid address; for burst mode, causes starting address to be latched. high = device ignores address inputs reset# = hardware reset input. low = device resets and returns to reading array data wp# = hardware write protect input. at v il , disables program and erase functions in the four highest and four lowest sectors. at v ih , does not protect any sectors. acc = at v hh , accelerates programming; automatically places device in unlock bypass mode. at v il , locks all sectors. should be at v ih for all other conditions. logic symbol 23 or 22 16 dq15?dq0 amax?a0 ce# oe# we# reset# clk rdy avd# wp# acc
10 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet ordering information the order number (valid combination) is formed by the following: valid combinations valid combinations list configurations planned to be supported in vol- ume for this device. consult the local amd sales office to confirm avail- ability of specific valid combinati ons and to check on newly released combinations. am29bds 128 h e 8 vk i temperature range i = industrial (?40 c to +85 c) package type vk = 80-ball fine-pitch ball grid array (bga) 0.80 mm pitch, 11.5 x 9 mm package (vbb080) vf = 80-ball fine-pitch ball grid array (bga) 0.80 mm pitch, 11.5 x 9mm, pb-free package (vbb080) vm = 64-ball fine-pitch ball grid array (bga) 0.80 mm pitch, 8 x 9 mm package (vbd064) v io and handshaking options 8= v io = 1.8 v, reduced wait-state handshaking enabled 9= v io = 1.8 v, standard handshaking speed e = 66 mhz d = 54 mhz process technology h = 0.13 m density 128 = 128 mbit (8 m x 16-bit) 64 = 64 mbit (4 m x 16-bit) device family am29bds cmos flash memory, simultaneous read/write, burst mode flash memory, 1.8 volt-only read, program, and erase valid combinations burst frequency (mhz) density order number package marking am29bds128he8 vki bs128he8v 66 128 mbit am29bds128he9 bs128he9v am29bds128hd8 bs128hd8v 54 am29bds128hd9 bs128hd9v am29bds128he8 vfi bs128he8vf 66 am29bds128he9 bs128he9vf am29bds128hd8 bs128hd8vf 54 am29bds128hd9 bs128hd9vf am29bds640he8 vmi bs640he8v 66 64 mbit am29bds640he9 bs640he9v am29bds640hd8 bs640hd8v 54 am29bds640hd9 bs640hd9v
may 10, 2006 27024b3 am29bds128h/am29bds640h 11 data sheet device bus operations this section describes the requirements and use of the device bus operations, which are initiated through the internal command register. the command register itself does not occupy an y addressable memory loca- tion. the register is composed of latches that store the commands, along with the address and data informa- tion needed to execute the command. the contents of the register serve as inputs to the internal state machine. the state machine outputs dictate the func- tion of the device. ta b l e 1 lists the device bus opera- tions, the inputs and control levels they require, and the resulting output. the following subsections describe each of these operations in further detail. table 1. device bus operations legend: l = logic 0, h = logic 1, x = don?t care, s = stable logic 0 or 1 but no transitions. note: default active edge of clk is the rising edge. requirements for asynchronous read operation (non-burst) to read data from the memo ry array, the system must first assert a valid address on amax?a0, while driving avd# and ce# to v il . we# should remain at v ih . the rising edge of avd# latche s the address. the data will appear on dq15?dq0. since the memory array is divided into four banks, each bank remains enabled for read access until the command register contents are altered. address access time (t acc ) is equal to the delay from stable addresses to valid output data. the chip enable access time (t ce ) is the delay from the stable addresses and stable ce# to valid data at the outputs. the output enable access time (t oe ) is the delay from the falling edge of oe# to va lid data at the output. the internal state machine is set for reading array data in asynchronous mode upon device power-up, or after a hardware reset. this ensures that no spurious alter- ation of the memory content occurs during the power transition. requirements for synchronous (burst) read operation the device is capable of continuous sequential burst operation and linear burst operation of a preset length. when the device first powers up, it is enabled for asyn- chronous read operation. prior to entering burst mode, the system should deter- mine how many wait states are desired for the initial word (t iacc ) of each burst access, what mode of burst operation is desired, whic h edge of the clock will be the operation ce# oe# we# amax?0 dq15?0 reset# clk (see note) avd# asynchronous read - addresses latched l l h addr in i/o h x asynchronous read - addresses steady state l l h addr in i/o h x l asynchronous write l h l addr in i/o h x l synchronous write l h l addr in i/o h standby (ce#) h x x high z high z h x x hardware reset x x x high z high z l x x burst read operations load starting burst address l x h addr in x h advance burst to next address with appropriate data presented on the data bus llhhigh z burst data out hh terminate current burst read cycle h x h high z high z h x terminate current burst read cycle via reset# x x h high z high z l x x terminate current burst read cycle and start new burst read cycle l x h high z i/o h
12 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet active clock edge, and how the rdy signal will transi- tion with valid data. the system would then write the configuration register command sequence. see ?set configuration register command sequence? section on page 33 and ?command definitions? section on page 33 for further details. once the system has written the ?set configuration register? command sequence, the device is enabled for synchronous reads only. the initial word is output t iacc after the active edge of the first clk cycle. subsequent words are output t bacc after the active edge of each successive clock cycle, which automatically increments the internal address counter. note that the device has a fixed internal address boundary that occurs every 64 words, starting at address 00003fh. during the time the device is out- putting data at this fixed internal address boundary (address 00003fh, 00007fh, 0000bfh, etc.), a two cycle latency occurs before data appears for the next address (address 000040h, 000080h, 0000c0h, etc.). the rdy output indicates this condition to the system by pulsing low. for standard handshaking devices, there is no two cycle latency between 3fh and 40h (or offset from these values by a multiple of 64) if the latched address was 3eh or 3fh or offset from these values by a multiple of 64). see figure 46, ?latency with boundary crossing,? on page 80 . for reduced wait-state handshaking devices, if the address latched is 3eh or 3fh (or offset from these values by a multiple of 64) two additional cycle latency occurs prior to the initial access and the two cycle latency between 3fh and 40h (or offset from these values by a multiple of 64) will not occur. the device will continue to output sequential burst data, wrapping around to address 000000h after it reaches the highest addressable memory location, until the system drives ce# high, reset# low, or avd# low in conjunction with a new address. see table 1, ?device bus operations,? on page 11 . if the host system crosses the bank boundary while reading in burst mode, and the device is not program- ming or erasing, a two-cycle latency will occur as described above in the subsequent bank. if the host system crosses the bank boundary while the device is programming or erasing, the device will provide read status information. the cloc k will be ignored. after the host has completed status reads, or the device has completed the program or erase operation, the host can restart a burst operation using a new address and avd# pulse. if the clock frequency is less than 6 mhz during a burst mode operation, additional latencies will occur. rdy indicates the length of the latency by pulsing low. 8-, 16-, and 32-word linear burst with wrap around the remaining three modes are of the linear wrap around design, in which a fixed number of words are read from consecutive addresses. in each of these modes, the burst addresses read are determined by the group within which the starting address falls. the groups are sized according to the number of words read in a single burst sequence for a given mode (see ta b l e 2 .) table 2. burst address groups as an example: if the starting address in the 8-word mode is 39h, the address range to be read would be 38-3fh, and the burst sequence would be 39-3a-3b-3c-3d-3e-3f-38h-etc. the burst sequence begins with the starting address written to the device, but wraps back to the first address in the selected group. in a similar fashion, the 16-word and 32-word linear wrap modes begin their burst sequence on the starting address written to the device, and then wrap back to the first address in the selected address group. note that in these three burst read modes the address pointer does not cross the boundary that occurs every 64 words; thus, no wait states are inserted (except during the initial access). the rdy pin indicates when data is valid on the bus. the devices can wrap through a maximum of 128 words of data (8 words up to 16 times, 16 words up to 8 times, or 32 words up to 4 times) before requiring a new synchronous access (latching of a new address). burst suspend/resume the burst suspend/resume feature allows the system to temporarily suspend a synchronous burst operation during the initial access (before data is available) or after the device is outputting data. when the burst operation is suspended, any previously latched internal data and the current state are retained. burst suspend requires ce# to be asserted, we# de-asserted, and the initial address latched by avd# or the clk edge. burst suspend occurs when oe# is de-asserted. see figure 21, ?reduced wait-state handshake burst suspend/resume at an even address,? on page 61, figure 22, ?reduced wait-state handshake burst suspend/resume at an odd address,? on page 61, figure 23, ?reduced wait-state handshake burst suspend/resume at address 3eh (or offset from 3eh),? on page 62, figure 24, ?reduced wait-state handshake burst suspend/resume at mode group size group address ranges 8-word 8 words 0-7h, 8-fh, 10-17h,... 16-word 16 words 0-fh, 10-1fh, 20-2fh,... 32-word 32 words 00-1fh, 20-3fh, 40-5fh,...
may 10, 2006 27024b3 am29bds128h/am29bds640h 13 data sheet address 3fh (or offset from 3fh by a multiple of 64),? on page 62, figure 25, ?standard handshake burst suspend prior to initial access,? on page 63, figure 26, ?standard handshake burst suspend at or after initial access,? on page 63, figure 27, ?standard handshake burst suspend at address 3fh (starting address 3dh or earlier),? on page 64, figure 28, ?standard hand- shake burst suspend at address 3eh/3fh (without a valid initial access),? on page 64, and figure 29, ?stan- dard handshake burst suspend at address 3eh/3fh (with 1 access clk),? on page 65. burst plus burst suspend should not last longer than t rcc without re-latching an address or crossing an address boundary. to resume the burst access, oe# must be re-asserted. the next active clk edge will resume the burst sequence where it had been sus- pended. see figure 30, ?read cycle for continuous suspend,? on page 65. the rdy pin is only controlled by ce#. rdy will remain active and is not placed into a high-impedance state when oe# is de-asserted. configuration register the device uses a configuration register to set the various burst parameters: number of wait states, burst read mode, active clock edge, rdy configuration, and synchronous mode active. reduced wait-state handshaking option the device can be equipped with a reduced wait-state handshaking feature that allows the host system to simply monitor the rdy signal from the device to deter- mine when the initial word of burst data is ready to be read. the host system should use the programmable wait state configuration to set the number of wait states for optimal burst mode operation. the initial word of burst data is indicated by the rising edge of rdy after oe# goes low. the presence of the reduced wait-state handshaking feature may be verified by writing the autoselect command sequence to the device. see ?autoselect command sequence? for details. for optimal burst mode performance on devices without the reduced wait-state handshaking option, the host system must set the appropriate number of wait states in the flash device depending on clock frequency and the presence of a boundary crossing. see ?set configuration register command sequence? section on page 33 section for more information. the device will automatically delay rdy a nd data by one additional clock cycle when the starting address is odd. the autoselect function allows the host system to determine whether the flash device is enabled for reduced wait-state handshaking. see the ?autoselect command sequence? section for more information. simultaneous read/writ e operations with zero latency this device is capable of reading data from one bank of memory while programming or erasing in another bank of memory. an erase operation may also be suspended to read from or program to another location within the same bank (except the sector being erased). figure 49, ?back-to-back r ead/write cycle timings,? on page 83 shows how read and write cycles may be initiated for simultaneous operation with zero latency. refer to the dc characteristics table for read-while-program and read-while-erase current specifications. writing commands/command sequences the device has the capability of performing an asyn- chronous or synchronous write operation. while the device is configured in asynchronous read it is able to perform asynchronous write operations only. clk is ignored in the asynchronous programming mode. when in the synchronous read mode configuration, the device is able to perform both asynchronous and syn- chronous write operations. clk and we# address latch is supported in the synchronous programming mode. during a synchronous write operation, to write a command or command sequence (which includes pro- gramming data to the device and erasing sectors of memory), the system must drive avd# and ce# to v il , and oe# to v ih when providing an address to the device, and drive we# and ce# to v il , and oe# to v ih when writing commands or data. during an asynchro- nous write operation, the system must drive ce# and we# to v il and oe# to v ih when providing an address, command, and data. addresses are latched on the last falling edge of we# or ce#, wh ile data is latched on the 1st rising edge of we# or ce#. the asynchronous and synchronous programing operation is independent of the set device read mode bit in the configuration register (see table 18, ?configuration register,? on page 36 ). the device features an unlock bypass mode to facili- tate faster programming. once the device enters the unlock bypass mode, only two write cycles are required to program a word, instead of four. an erase operation can erase one sector, multiple sec- tors, or the entire device. table 12, ?am29bds128h sector address table,? on page 27 indicates the address space that each sector occupies. the device address space is divided into four banks: banks b and c contain only 32 kword sectors, while banks a and d contain both 4 kword boot sectors in addition to 32 kword sectors. a ?bank address? is the address bits required to uniquely select a bank. similarly, a ?sector address? is the address bits required to uniquely select a sector.
14 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet i cc2 in the ?dc characteristics? section on page 54 represents the active current specification for the write mode. the ac characteristics section contains timing specification tables and timing diagrams for write oper- ations. accelerated program operation the device offers accelerated program operations through the acc function. acc is primarily intended to allow faster manufacturing throughput at the factory. if the system asserts v hh on this input, the device auto- matically enters the aforementioned unlock bypass mode and uses the higher voltage on the input to reduce the time required for program operations. the system would use a two-cycle program command sequence as required by the unlock bypass mode. removing v hh from the acc input returns the device to normal operation. note that sectors must be unlocked prior to raising acc to v hh . note that the acc pin must not be at v hh for operations other than accelerated programming, or device damage may result. in addition, the acc pin must not be left floating or unconnected; inconsistent behavior of the device may result . when at v il , acc locks all sectors. acc should be at v ih for all other conditions. autoselect mode the autoselect mode provides manufacturer and de- vice identification, and sector protection verification, through identifier codes output from the internal regis- ter (which is separate from the memory array) on dq15?dq0. this mode is primarily intended for pro- gramming equipment to automatically match a device to be programmed with its corresponding program- ming algorithm. however, the autoselect codes can also be accessed in-system through the command register. when using programming equipment, the autoselect mode requires v id on address pin a9. address pins must be as shown in table 3, ?autoselect codes (high voltage method),? on page 15 . in addition, when verify- ing sector protection, the sector address must appear on the appropriate highest order address bits (see table 4, ?am29bds128h boot sector/sector block addresses for protection/unprotection,? on page 16 ). ta b l e 3 shows the remaining address bits that are don?t care. when all necessary bits have been set as required, the programming equipment may then read the corresponding identifier code on dq15?dq0. however, the autoselect codes can also be accessed in-system through the command register, for instances when the device is erased or programmed in a system without access to high voltage on the a9 pin. the com- mand sequence is illustrated in table 20, ?memory array command definitions,? on page 46 . note that if a bank address (ba) is asserted during the third write cycle of the autoselect command, the host system can read autoselect data that bank and then immediately read array data from the other bank, without exiting the autoselect mode. to access the autoselect codes in-system, the host system can issue the autoselect command via the command register, as shown in table 20, ?memory array command definitions,? on page 46 . this method does not require v id . autoselect mode may only be en- tered and used when in the asynchronous read mode. refer to the ?autoselect command sequence? section on page 36 for more information.
may 10, 2006 27024b3 am29bds128h/am29bds640h 15 data sheet table 3. autoselect codes (high voltage method) legend: l = logic low = v il , h = logic high = v ih , ba = bank address, sa = sector address, x = don?t care. notes: 1. the autoselect codes may also be accessed in-system via command sequences. 2. ppb protection status is shown on the data bus description ce# oe# we# reset# amax to a12 a11 to a10 a9 a8 a7 a6 a5 to a4 a3 a2 a1 a0 dq15 to dq0 manufacturer id : amd llh h x x v id x x l x l l l l 0001h device id read cycle 1 llh h x x v id xl l l l l l h 227eh read cycle 2 hhhl 2218h (128 mb) 221eh (64 mb) read cycle 3 hhhh 2200h (128 mb) 2201h (64 mb) sector protection verification llh h sax v id xl l lllhl 0001h (protected), 0000h (unprotected) indicator bits l l h h x x v id xxlxllhh dq15 - dq8 = 0 dq7 - factory lock bit 1 = locked, 0 = not locked dq6 -customer lock bit 1 = locked, 0 = not locked dq5 = handshake bit 1 = reduced wait-state handshake, 0 = standard handshake dq4 - dq0 = 0 hardware sector group protection llh h sax v id xxx ll lhl 0001h (protected), 0000h (unprotected)
16 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet table 4. am29bds128h boot sector/sector block addresses for protection/unprotection sector a22?a12 sector/ sector block size sa0 00000000000 4 kwords sa1 00000000001 4 kwords sa2 00000000010 4 kwords sa3 00000000011 4 kwords sa4 00000000100 4 kwords sa5 00000000101 4 kwords sa6 00000000110 4 kwords sa7 00000000111 4 kwords sa8 00000001xxx 32 kwords sa9 00000010xxx 32 kwords sa10 00000011xxx 32 kwords sa11?sa14 000001xxxxx 128 (4x32) kwords sa15?sa18 000010xxxxx 128 (4x32) kwords sa19?sa22 000011xxxxx 128 (4x32) kwords sa23-sa26 000100xxxxx 128 (4x32) kwords sa27-sa30 000101xxxxx 128 (4x32) kwords sa31-sa34 000110xxxxx 128 (4x32) kwords sa35-sa38 000111xxxxx 128 (4x32) kwords sa39-sa42 001000xxxxx 128 (4x32) kwords sa43-sa46 001001xxxxx 128 (4x32) kwords sa47-sa50 001010xxxxx 128 (4x32) kwords sa51?sa54 001011xxxxx 128 (4x32) kwords sa55?sa58 001100xxxxx 128 (4x32) kwords sa59?sa62 001101xxxxx 128 (4x32) kwords sa63?sa66 001110xxxxx 128 (4x32) kwords sa67?sa70 001111xxxxx 128 (4x32) kwords sa71?sa74 010000xxxxx 128 (4x32) kwords sa75?sa78 010001xxxxx 128 (4x32) kwords sa79?sa82 010010xxxxx 128 (4x32) kwords sa83?sa86 010011xxxxx 128 (4x32) kwords sa87?sa90 010100xxxxx 128 (4x32) kwords sa91?sa94 010101xxxxx 128 (4x32) kwords sa95?sa98 010110xxxxx 128 (4x32) kwords sa99?sa102 010111xxxxx 128 (4x32) kwords sa103?sa106 011000xxxxx 128 (4x32) kwords sa107?sa110 011001xxxxx 128 (4x32) kwords sa111?sa114 011010xxxxx 128 (4x32) kwords sa115?sa118 011011xxxxx 128 (4x32) kwords sa119?sa122 011100xxxxx 128 (4x32) kwords sa123?sa126 011101xxxxx 128 (4x32) kwords sa127?sa130 011110xxxxx 128 (4x32) kwords sa131-sa134 011111xxxxx 128 (4x32) kwords sa135-sa138 100000xxxxx 128 (4x32) kwords sa139-sa142 100001xxxxx 128 (4x32) kwords sa143-sa146 100010xxxxx 128 (4x32) kwords sa147-sa150 100011xxxxx 128 (4x32) kwords sa151?sa154 100100xxxxx 128 (4x32) kwords sa155?sa158 100101xxxxx 128 (4x32) kwords sa159?sa162 100110xxxxx 128 (4x32) kwords sa163?sa166 100111xxxxx 128 (4x32) kwords sa167?sa170 101000xxxxx 128 (4x32) kwords sa171?sa174 101001xxxxx 128 (4x32) kwords sa175?sa178 101010xxxxx 128 (4x32) kwords sa179?sa182 101011xxxxx 128 (4x32) kwords sa183?sa186 101100xxxxx 128 (4x32) kwords sa187?sa190 101101xxxxx 128 (4x32) kwords sa191?sa194 101110xxxxx 128 (4x32) kwords sa195?sa198 101111xxxxx 128 (4x32) kwords sa199?sa202 110000xxxxx 128 (4x32) kwords sa203?sa206 110001xxxxx 128 (4x32) kwords sa207?sa210 110010xxxxx 128 (4x32) kwords sa211?sa214 110011xxxxx 128 (4x32) kwords sa215?sa218 110100xxxxx 128 (4x32) kwords sa219?sa222 110101xxxxx 128 (4x32) kwords sa223?sa226 110110xxxxx 128 (4x32) kwords sa227?sa230 110111xxxxx 128 (4x32) kwords sa231?sa234 111000xxxxx 128 (4x32) kwords sa235?sa238 111001xxxxx 128 (4x32) kwords sa239?sa242 111010xxxxx 128 (4x32) kwords sa243?sa246 111011xxxxx 128 (4x32) kwords sa247?sa250 111100xxxxx 128 (4x32) kwords sa251?sa254 111101xxxxx 128 (4x32) kwords sa255?sa258 111110xxxxx 128 (4x32) kwords sa259 11111100xxx 32 kwords sa260 11111101xxx 32 kwords sa261 11111110xxx 32 kwords sa262 11111111000 4 kwords sa263 11111111001 4 kwords sa264 11111111010 4 kwords sa265 11111111011 4 kwords sa266 11111111100 4 kwords sa267 11111111101 4 kwords sa268 11111111110 4 kwords sa269 11111111111 4 kwords sector a22?a12 sector/ sector block size
may 10, 2006 27024b3 am29bds128h/am29bds640h 17 data sheet table 5. am29bds640h boot sector/sector block addresses for protection/unprotection sector/sector block protection and un- protection the hardware sector protection feature disables both programming and erase operations in any sector. the hardware sector unprotection feature re-enables both program and erase operations in previously protected sectors. sector protection/unprotection can be imple- mented via two methods. (note: for the following discussion, the term ?sector? applies to both sectors and sector blocks. a sector block consists of two or more adjacent sectors that are protected or unprotected at the same time (see ta b l e 4 , ?am29bds128h boot sector/sector block addresses for protection/unprotection,? on page 16 sector protection the am29bdsxxxh family f eatures several levels of sector protection, which can disable both the program and erase operations in certain sectors or sector groups: persistent sector protection a command sector protection method that replaces the old 12 v controlled protection method. password sector protection a highly sophisticated protec tion method that requires a password before changes to certain sectors or sec- tor groups are permitted wp# hardware protection a write protect pin that can prevent program or erase operations in the outermost sectors. the wp# hardware protection feature is always avail- able, independent of the software managed protection method chosen. selecting a sector protection mode all parts default to operate in the persistent sector protection mode. the customer must then choose if the persistent or password protection method is most desirable. there are two one-time programmable non-volatile bits that define which sector protection method will be used. if the customer decid es to con- tinue using the persistent sector protection method, they must set the persistent sector protection mode sector a21?a12 sector/ sector block size sa0 0000000000 4 kwords sa1 0000000001 4 kwords sa2 0000000010 4 kwords sa3 0000000011 4 kwords sa4 0000000100 4 kwords sa5 0000000101 4 kwords sa6 0000000110 4 kwords sa7 0000000111 4 kwords sa8 0000001xxx 32 kwords sa9 0000010xxx 32 kwords sa10 0000011xxx 32 kwords sa11?sa14 00001xxxxx 128 (4x32) kwords sa15?sa18 00010xxxxx 128 (4x32) kwords sa19?sa22 00011xxxxx 128 (4x32) kwords sa23-sa26 00100xxxxx 128 (4x32) kwords sa27-sa30 00101xxxxx 128 (4x32) kwords sa31-sa34 00110xxxxx 128 (4x32) kwords sa35-sa38 00111xxxxx 128 (4x32) kwords sa39-sa42 01000xxxxx 128 (4x32) kwords sa43-sa46 01001xxxxx 128 (4x32) kwords sa47-sa50 01010xxxxx 128 (4x32) kwords sa51?sa54 01011xxxxx 128 (4x32) kwords sa55?sa58 01100xxxxx 128 (4x32) kwords sa59?sa62 01101xxxxx 128 (4x32) kwords sa63?sa66 01110xxxxx 128 (4x32) kwords sa67?sa70 01111xxxxx 128 (4x32) kwords sa71?sa74 10000xxxxx 128 (4x32) kwords sa75?sa78 10001xxxxx 128 (4x32) kwords sa79?sa82 10010xxxxx 128 (4x32) kwords sa83?sa86 10011xxxxx 128 (4x32) kwords sa87?sa90 10100xxxxx 128 (4x32) kwords sa91?sa94 10101xxxxx 128 (4x32) kwords sa95?sa98 10110xxxxx 128 (4x32) kwords sa99?sa102 10111xxxxx 128 (4x32) kwords sa103?sa106 11000xxxxx 128 (4x32) kwords sa107?sa110 11001xxxxx 128 (4x32) kwords sa111?sa114 11010xxxxx 128 (4x32) kwords sa115?sa118 11011xxxxx 128 (4x32) kwords sa119?sa122 11100xxxxx 128 (4x32) kwords sa123?sa126 11101xxxxx 128 (4x32) kwords sa127?sa130 11110xxxxx 128 (4x32) kwords sa131 1111100xxx 32 kwords sa132 1111101xxx 32 kwords sa133 1111110xxx 32 kwords sa134 1111111000 4 kwords sa135 1111111001 4 kwords sa136 1111111010 4 kwords sa137 1111111011 4 kwords sa138 1111111100 4 kwords sa139 1111111101 4 kwords sa140 1111111110 4 kwords sa141 1111111111 4 kwords sector a21?a12 sector/ sector block size
18 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet locking bit . this will permanently set the part to op- erate only using persistent sector protection. if the customer decides to use the password method, they must set the password mode locking bit . this will permanently set the part to operate only using pass- word sector protection. it is important to remember that setting either the per- sistent sector protection mode locking bit or the password mode locking bit permanently selects the protection mode. it is not possible to switch between the two methods once a locking bit has been set. it is important that one mode is explicitly selected when the device is first programmed, rather than relying on the default mode alone. this is so that it is not possible for a system program or virus to later set the password mode locking bit, which would cause an unexpected shift from the default persistent sector protection mode into the password protection mode. the device is shipped with all sectors unprotected. amd offers the option of programming and protecting sectors at the factory prior to shipping the device through amd?s expressflash? service. contact an amd representative for details. it is possible to determine whether a sector is pro- tected or unprotected. see ?autoselect command se- quence? section on page 36 for details. persistent sector protection the persistent sector protection method replaces the old 12 v controlled protection method while at the same time enhancing flexibility by providing three dif- ferent sector protection states: persistently locked ?a sector is protected and cannot be changed. dynamically locked ?the sector is protected and can be changed by a simple command unlocked ?the sector is unprotected and can be changed by a simple command in order to achieve these states, three types of ?bits? are going to be used: persistent protection bit (ppb) a single persistent (non-volatile) protection bit is as- signed to a maximum four sectors ( ?am29bds128h boot sector/sector block addresses for protec- tion/unprotection? section on page 16 ). all 4 kbyte boot-block sectors have individual sector persistent protection bits (ppbs) for greater flexibility. each ppb is individually modifiable through the ppb program command . note: if a ppb requires erasure, all of the sector ppbs must first be preprogrammed prior to ppb erasing. all ppbs erase in parallel, un like programming where in- dividual ppbs are programmable. it is the responsibil- ity of the user to perform the preprogramming operation. otherwise, an already erased sector ppbs has the potential of being over-erased. there is no hardware mechanism to prevent sector ppbs over-erasure. persistent protection bit lock (ppb lock) a global volatile bit. when set to ?1?, the ppbs cannot be changed. when cleared (?0?), the ppbs are changeable. there is only one ppb lock bit per de- vice. the ppb lock is cleared after power-up or hard- ware reset. there is no command sequence to unlock the ppb lock. dynamic protection bit (dyb) a volatile protection bit is assigned for each sector. after power-up or hardware reset, the contents of all dybs is ?0?. each dyb is individually modifiable through the dyb write command. when the parts are first shipped, the ppbs are cleared. the dybs and ppb lock are defaulted to power up in the cleared st ate ? meaning the ppbs are changeable. when the device is first powered on the dybs power up cleared (sectors not protected). the protection state for each sector is determined by the logical or of the ppb and the dyb related to that sector. for the sectors that have the ppbs cleared, the dybs control whether or not the sector is protected or unprotected. by issuing the dyb write command sequences, the dybs will be set or cleared, th us placing each sector in the protected or unprotected state. these are the so-called dynamic locked or unlocked states. they are called dynamic states because it is very easy to switch back and forth between the protected and un- protected conditions. this allows software to easily protect sectors against inadvertent changes yet does not prevent the easy removal of protection when changes are needed. the dybs maybe set or cleared as often as needed. the ppbs allow for a more static, and difficult to change, level of protection. the ppbs retain their state across power cycles because they are non-volatile. individual ppbs are set with a command but must all be cleared as a group through a complex sequence of program and erasing commands. the ppbs are also limited to 100 erase cycles. the pbb lock bit adds an additional level of protec- tion. once all ppbs are programmed to the desired settings, the ppb lock may be set to ?1?. setting the ppb lock disables all program and erase commands to the non-volatile ppbs. in effect, the ppb lock bit locks the ppbs into their curr ent state. the only way to clear the ppb lock is to go through a power cycle.
may 10, 2006 27024b3 am29bds128h/am29bds640h 19 data sheet system boot code can determine if any changes to the ppb are needed e.g. to a llow new system code to be downloaded. if no changes are needed then the boot code can set the ppb lock to disable any further changes to the ppbs du ring system operation. the wp# write protect pin adds a final level of hard- ware protection to the four highest and four lowest 4 kbyte sectors. when this pin is low it is not possible to change the contents of these four sectors. these sec- tors generally hold system boot code. so, the wp# pin can prevent any changes to the boot code that could override the choices made while setting up sector pro- tection during system initialization. it is possible to have sectors that have been persis- tently locked, and sectors that are left in the dynamic state. the sectors in the dynamic state are all unpro- tected. if there is a need to protect some of them, a simple dyb write command sequence is all that is necessary. the dyb write command for the dynamic sectors switch the dybs to signify protected and un- protected, respectively. if there is a need to change the status of the persistently locked sectors, a few more steps are required. first, the ppb lock bit must be dis- abled by either putting the device through a power-cy- cle, or hardware reset. the ppbs can then be changed to reflect the desired settings. setting the ppb lock bit once again will lock the ppbs, and the de- vice operates normally again. note: to achieve the best protection, it?s recommended to execute the ppb lock bit set command early in the boot code, and protect the boot code by holding wp# = v il . table 6. sector protection schemes ta bl e 6 contains all possible combinations of the dyb, ppb, and ppb lock relating to the status of the sector. in summary, if the ppb is set, and the ppb lock is set, the sector is protected and the protection can not be removed until the next power cycle clears the ppb lock. if the ppb is cleared, the sector can be dynami- cally locked or unlocked. the dyb then controls whether or not the sector is protected or unprotected. if the user attempts to program or erase a protected sector, the device ignores the command and returns to read mode. a program command to a protected sector enables status polling for approximately t psp before the device returns to read mode without having modi- fied the contents of the protected sector. an erase command to a protected sector enables status polling for approximately t sea after which the device returns to read mode without having erased the protected sec- tor. the programming of the dy b, ppb, and ppb lock for a given sector can be verified by writing a dyb/ppb/ppb lock verify command to the device. persistent sector protection mode locking bit like the password mode locking bit, a persistent sec- tor protection mode locking bit exists to guarantee that the device remain in software sector protection. once set, the persistent sector protection locking bit pre- vents programming of the password protection mode locking bit. this guarantees that a hacker could not place the device in password protection mode. password protection mode the password sector protection mode method allows an even higher level of security than the persistent sector protection mode. there are two main differ- ences between the persistent sector protection and the password sector protection mode: when the device is first powered on, or comes out of a reset cycle, the ppb lock bit is set to the locked state , rather than cleared to the unlocked state. the only means to clear the ppb lock bit is by writ- ing a unique 64-bit password to the device. the password sector protection method is otherwise identical to the persistent sector protection method. a 64-bit password is the only additional tool utilized in this method. the password is stored in a one-time programmable (otp) region of the flash memory. once the password mode locking bit is set, the password is permanently set with no means to read, program, or erase it. the password is used to clear the ppb lock bit. the pass- word unlock command must be written to the flash, along with a password. the flash device internally compares the given password with the pre-pro- dyb ppb ppb lock sector state 000 unprotected?ppb and dyb are changeable 001 unprotected?ppb not changeable, dyb is changeable 010 protected?ppb and dyb are changeable 100 110 011 protected?ppb not changeable, dyb is changeable 101 111
20 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet grammed password. if they match, the ppb lock bit is cleared, and the ppbs can be altered. if they do not match, the flash device does nothing. there is a built-in 2 s delay for each ?password check.? this delay is intended to thwart any efforts to run a program that tries all possible combinations in order to crack the password. password and password mode locking bit in order to select the password sector protection scheme, the customer must first program the pass- word. it is recommended that the password be somehow correlated to the unique electronic serial number (esn) of the particular flash device. each esn is different for every flash device; therefore each pass- word should be different for every flash device. while programming in the password region, the customer may perform password verify operations. once the desired password is programmed in, the customer must then set the password mode locking bit. this operation achieves two objectives: 1. it permanently sets the device to operate using the password protection mode. it is not possible to re- verse this function. 2. it also disables all further commands to the pass- word region. all program, and read operations are ignored. both of these objectives are important, and if not care- fully considered, may lead to unrecoverable errors. the user must be sure that the password protection method is desired when setting the password mode locking bit. more importantly, the user must be sure that the password is correct when the password mode locking bit is set. due to the fact that read operations are disabled, there is no means to verify what the password is afterwards. if the password is lost after setting the password mode locking bit, there will be no way to clear the ppb lock bit. the password mode locking bit, once set, prevents reading the 64-bit password on the dq bus and further password programming. the password mode locking bit is not erasable. once password mode locking bit is programmed, the persistent sector protection lock- ing bit is disabled from programming, guaranteeing that no changes to the protection scheme are allowed. 64-bit password the 64-bit password is located in its own memory space and is accessible through the use of the pass- word program and verify commands (see ?password program command? section on page 40 and ?pass- word verify command? section on page 40 ). the password function works in conjunction with the pass- word mode locking bit, which when set, prevents the password verify command from reading the contents of the password on the pins of the device. persistent protection bit lock the persistent protection bit (ppb) lock is a volatile bit that reflects the state of the password mode lock- ing bit after power-up reset. if the password mode lock bit is also set, after a hardware reset (reset# asserted) or a power-up reset the only means for clearing the ppb lock bit in password protection mode is to issue the password unlock command. suc- cessful execution of the password unlock command clears the ppb lock bit, allowing for sector ppbs modifications. asserting reset#, taking the device through a power-on reset, or issuing the ppb lock bit set command sets the ppb lock bit to a ?1?. if the password mode locking bit is not set, including persistent protection mode, the ppb lock bit is cleared after power-up or hardware reset. the ppb lock bit can be set by issuing the ppb lock bit set command. once set the only means for clearing the ppb lock bit is by issuing a hardware or power-up re- set. the password unlock command is ignored in per- sistent protection mode. high voltage sector protection sector protection and unprotection may also be imple- mented using programming equipment. the procedure requires high voltage (v id ) to be placed on the reset# pin. refer to figure 2, ?in-system sector pro- tection/ sector unprotection algorithms,? on page 22 for details on this procedure. note that for sector unpro- tect, all unprotected sectors must be first protected prior to the first sector write cycle. once the password mode locking bit or persistent protection locking bit are set, the high voltage sector protect/unprotect capa- bility is disabled. standby mode when the system is not reading or writing to the device, it can place the device in the standby mode. in this mode, current consumption is greatly reduced, and the outputs are placed in the high impedance state, inde- pendent of the oe# input. the device enters the cmos standby mode when the ce# and reset# inputs are both held at v cc 0.2 v. the device requires standard access time (t ce ) for read access, before it is ready to read data. if the device is deselected during erasure or program- ming, the device draws active current until the opera- tion is completed. i cc3 in the ?dc characteristics? section on page 54 represents the standby current specification.
may 10, 2006 27024b3 am29bds128h/am29bds640h 21 data sheet automatic sleep mode the automatic sleep mode minimizes flash device energy consumption. while in asynchronous mode, the device automatically enables this mode when addresses remain stable for t acc + 60 ns. the auto- matic sleep mode is independent of the ce#, we#, and oe# control signals. standard address access timings provide new data when addresses are changed. while in sleep mode, output data is latched and always avail- able to the system. while in synchronous mode, the device automatically enables this mode when either the first active clk level is greater than t acc or the clk runs slower than 5 mhz. note that a new burst opera- tion is required to provide new data. i cc6 in the ?dc characteristics? section on page 54 represents the automatic sleep mode current specifica- tion. reset#: hardwa re reset input the reset# input provides a hardware method of resetting the device to reading array data. when reset# is driven low for at least a period of t rp , the device immediately terminates any operation in progress, tristates all outputs, resets the configuration register, and ignores all read/write commands for the duration of the reset# puls e. the device also resets the internal state machine to reading array data. the operation that was interrupted should be reinitiated once the device is ready to accept another command sequence, to ensure data integrity. current is reduced for the duration of the reset# pulse. when reset# is held at v ss 0.2 v, the device draws cmos standby current (i cc4 ). if reset# is held at v il but not within v ss 0.2 v, the standby current will be greater. reset# may be tied to the system reset circuitry. a system reset would thus also reset the flash memory, enabling the system to read the boot-up firmware from the flash memory. if reset# is asserted during a program or erase oper- ation, the device requires a time of t ready (during embedded algorithms) before the device is ready to read data again. if reset# is asserted when a program or erase operation is not executing, the reset operation is completed within a time of t ready (not during embedded algorithms). the system can read data t rh after reset# returns to v ih . refer to the ?ac characteristics? section on page 68 for reset# parameters and to figure 33, ?reset tim- ings,? on page 68 for the timing diagram. output disable mode when the oe# input is at v ih , output from the device is disabled. the outputs are placed in the high imped- ance state. figure 1. temporary sector unprotect operation start perform erase or program operations reset# = v ih temporary sector unprotect completed (note 2) reset# = v id (note 1) notes: 1. all protected sectors unprotected (if wp# = v il , outermost boot sectors will remain protected). 2. all previously protected sectors are protected once again.
22 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet figure 2. in-system sector protection/ sector unprotection algorithms sector protect: write 60h to sector address with a7 ? a0 = 00000010 set up sector address wait 150 s verify sector protect: write 40h to sector address with a7 ? a0 = 00000010 read from sector address with a7 ? a0 = 00000010 start plscnt = 1 reset# = v id wait 1 ms first write cycle = 60h? data = 01h? remove v id from reset# write reset command sector protect complete yes yes no plscnt = 25? yes device failed increment plscnt temporary sector unprotect mode no sector unprotect: write 60h to sector address with a7:a0 = 01000010 set up first sector address wait 1.5 ms verify sector unprotect: write 40h to sector address with a7 ? a0 = 00000010 read from sector address with a7 ? a0 = 00000010 start plscnt = 1 reset# = v id wait 1 ms data = 00h? last sector verified? remove v id from reset# write reset command sector unprotect complete yes no plscnt = 1000? yes device failed increment plscnt temporary secto r unprotect mode no all sectors protected? yes protect all sectors: the indicated portion of the sector protect algorithm must be performed for all unprotected sectors prior to issuing the first sector unprotect address set up next sector address no yes no yes no no yes no sector protect algorithm sector unprotect algorithm first write cycle = 60h? protect another sector? reset plscnt = 1
may 10, 2006 27024b3 am29bds128h/am29bds640h 23 data sheet secsi? (secured si licon) sector flash memory region the secsi (secured silicon) sector feature provides a flash memory region that enables permanent part identification through an electronic serial number (esn) the 128-word secsi sector is divided into 64 factory-lockable words that can be programmed and locked by the customer. the secsi sector is located at addresses 000000h-00007fh in both persistent pro- tection mode and password protection mode. it uses indicator bits (dq6, dq7) to indicate the fac- tory-locked and customer-locked status of the part. the system accesses the secsi sector through a command sequence (see ?enter secsi? sector/exit secsi sector command sequence?). after the system has written the enter secsi sector command se- quence, it may read the secsi sector by using the ad- dresses normally occupied by the boot sectors. this mode of operation contin ues until the system issues the exit secsi sector command sequence, or until power is removed from the device. on power-up, or following a hardware reset, the device reverts to send- ing commands to the normal address space. factory-locked area (64 words) the factory-locked area of the secsi sector (000000h-00003fh) is locked when the part is shipped, whether or not the area was programmed at the factory. the secsi sector factory-locked indicator bit (dq7) is permanently set to a ?1?. amd offers the expressflash service to program the factory-locked area with a random esn, a customer-defined code, or any combination of the two. because only amd can program and protect the factory-locked area, this method ensures the security of the esn once the product is shipped to the field. contact an amd repre- sentative for details on using the amd expressflash service. table 7. secsi tm sector addresses customer-lockable area (64 words) the customer-lockable area of the secsi sector (000040h-00007fh) is shipped unprotected, which al- lows the customer to program and optionally lock the area as appropriate for the application. the secsi sector customer-locked indicator bit (dq6) is shipped as ?0? and can be permanently locked to ?1? by issuing the secsi protection bit program command. the secsi sector can be read any number of times, but can be programmed and locked only once. note that the accelerated programming (acc) and unlock by- pass functions are not available when programming the secsi sector. the customer-lockable secsi sector area can be pro- tected using one of the following procedures: write the three-cycle enter secsi sector region command sequence, and then follow the in-system sector protect algorithm as shown in figure 2, ex- cept that reset# may be at either v ih or v id . this allows in-system protection of the secsi sector re- gion without raising any device pin to a high voltage. note that this method is on ly applicable to the secsi sector. write the three-cycle enter secsi sector secure region command sequence, and then use the alter- nate method of sector protection described in the high voltage sector protection section. once the secsi sector is locked and verified, the sys- tem must write the exit secsi sector region com- mand sequence to return to reading and writing the remainder of the array. the secsi sector lock must be used with caution since, once locked, there is no procedure available for unlocking the secsi sector area and none of the bits in the secsi sector memory space can be modified in any way. secsi sector protection bits the secsi sector protection bits prevent program- ming of the secsi sector memory area. once set, the secsi sector memory area contents are non-modifi- able. hardware data protection the command sequence requirement of unlock cycles for programming or erasing provides data protection against inadvertent writes (refer to table 20, ?memory array command definitions,? on page 46 for command definitions). the device offers two types of data protection at the sector level: the ppb and dyb associ ated command se- quences disables or re-enables both program and erase operations in any sector or sector group. when wp# is at v il , the four outermost sectors are locked. when acc is at v il , all sectors are locked. the following hardware data protection measures prevent accidental erasure or programming, which might otherwise be caused by spurious system level signals during v cc power-up and power-down transi- tions, or from system noise. sector size address range am29bds128h/ am29bds640h 128 words 000000h?00007fh factory-locked area 64 words 000000h?00003fh customer-lockable area 64 words 000040h?00007fh
24 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet write protect (wp#) the write protect feature provides a hardware method of protecting the four outermost sectors. this function is provided by the wp# pin and overrides the previ- ously discussed sector pr otection/unprotection method. if the system asserts v il on the wp# pin, the device disables program and erase functions in the eight ?out- ermost? 4 kword boot sectors. if the system asserts v ih on the wp# pin, the device reverts to whether the boot sectors were last set to be protected or unprotected. that is, sector protection or unprotection for these sectors depends on whether they were last protected or unprotected using the method described in ?ppb program command? sec- tion on page 43 . note that the wp# pin must not be left floating or un- connected; inconsistent behavior of the device may re- sult. low v cc write inhibit when v cc is less than v lko , the device does not accept any write cycles. this protects data during v cc power-up and power-down. the command register and all internal program/erase circuits are disabled, and the device resets to reading array data. subsequent writes are ignored until v cc is greater than v lko . the system must provide the proper signals to the control inputs to prevent unintentional writes when v cc is greater than v lko . write pulse ?glitch? protection noise pulses of less than 5 ns (typical) on oe#, ce# or we# do not initiate a write cycle. logical inhibit write cycles are inhibited by holding any one of oe# = v il , ce# = v ih or we# = v ih . to initiate a write cycle, ce# and we# must be a logical zero while oe# is a logical one. power-up write inhibit if we# = ce# = reset# = v il and oe# = v ih during power up, the device does not accept commands on the rising edge of we#. the internal state machine is automatically reset to the read mode on power-up. common flash me mory interface (cfi) the common flash interface (cfi) specification out- lines device and host system software interrogation handshake, which allows specific vendor-specified software algorithms to be used for entire families of devices. software support can then be device-indepen- dent, jedec id-independent, and forward- and back- ward-compatible for the specified flash device families. flash vendors can standardize their existing interfaces for long-term compatibility. this device enters the cfi query mode when the system writes the cfi query command, 98h, to address 55h any time the device is ready to read array data. the system can read cfi information at the addresses given in tables 8-11 . to terminate reading cfi data, the system must write the reset command. the system can also write the cfi query command when the device is in the autoselect mode. the device enters the cfi query mode, and the system can read cfi data at the addresses given in tables 8-11 . the system must write the reset command to return the device to the autoselect mode. for further information, plea se refer to the cfi specifi- cation and cfi publication 100, available via the amd site at the following url: http://www.amd.com/flash/cfi. alternatively, contact an amd representative for copies table 8. cfi query identification string addresses data description 10h 11h 12h 0051h 0052h 0059h query unique ascii string ?qry? 13h 14h 0002h 0000h primary oem command set 15h 16h 0040h 0000h address for primary extended table 17h 18h 0000h 0000h alternate oem command set (00h = none exists) 19h 1ah 0000h 0000h address for alternate oem extended table (00h = none exists)
may 10, 2006 27024b3 am29bds128h/am29bds640h 25 data sheet table 9. system interface string table 10. device geometry definition addresses data description 1bh 0017h v cc min. (write/erase) d7?d4: volt, d3?d0: 100 millivolt 1ch 0019h v cc max. (write/erase) d7?d4: volt, d3?d0: 100 millivolt 1dh 0000h v pp min. voltage (00h = no v pp pin present) 1eh 0000h v pp max. voltage (00h = no v pp pin present) 1fh 0004h typical timeout per single byte/word write 2 n s 20h 0000h typical timeout for min. size buffer write 2 n s (00h = not supported) 21h 0009h typical timeout per individual block erase 2 n ms 22h 0000h typical timeout for full chip erase 2 n ms (00h = not supported) 23h 0004h max. timeout for byte/word write 2 n times typical 24h 0000h max. timeout for buffer write 2 n times typical 25h 0004h max. timeout per individual block erase 2 n times typical 26h 0000h max. timeout for full chip erase 2 n times typical (00h = not supported) addresses data description 27h 001xh device size = 2 n byte bds128h = 0018h; bds640h = 0017h 28h 29h 0001h 0000h flash device interface description (refer to cfi publication 100) 2ah 2bh 0000h 0000h max. number of bytes in multi-byte write = 2 n (00h = not supported) 2ch 0003h number of erase block regions within device 2dh 2eh 2fh 30h 0007h 0000h 0020h 0000h erase block region 1 information (refer to the cfi specification or cfi publication 100) 31h 32h 33h 34h 00xdh 0000h 0000h 0001h erase block region 2 information address 31h: bds128h = 00fdh; bds640h = 007dh 35h 36h 37h 38h 0007h 0000h 0020h 0000h erase block region 3 information 39h 3ah 3bh 3ch 0000h 0000h 0000h 0000h erase block region 4 information
26 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet table 11. primary vendor-specific extended query addresses data description 40h 41h 42h 0050h 0052h 0049h query-unique ascii string ?pri? 43h 0031h major version number, ascii 44h 0033h minor version number, ascii 45h 000ch address sensitive unlock (bits 1-0) 0 = required, 1 = not required silicon technology (bits 5-2) 0011 = 0.13 m 46h 0002h erase suspend 0 = not supported, 1 = to read only, 2 = to read & write 47h 0001h sector protect 0 = not supported, x = number of sectors in per group 48h 0000h sector temporary unprotect 00 = not supported, 01 = supported 49h 0007h sector protect/unprotect scheme 07 = advanced sector protection 4ah 00x7h simultaneous operation: number of sect ors in all banks except boot block bds128h = 00e7h; bds640h = 0077h 4bh 0001h burst mode type 00 = not supported, 01 = supported 4ch 0000h page mode type 00 = not supported, 01 = 4 word page, 02 = 8 word page, 04 = 16 word page 4dh 00b5h acc (acceleration) supply minimum 00h = not supported, d7-d4: volt, d3-d0: 100 mv 4eh 00c5h acc (acceleration) supply maximum 00h = not supported, d7-d4: volt, d3-d0: 100 mv 4fh 0001h boot sector flag 50h 0000h program suspend. 00h = not supported 57h 0004h bank organization: x = number of banks 58h 59h 5ah 5bh 0027h / 0017h 0060h / 0030h 0060h / 0030h 0027h / 0017h bank a ? bank d region information. x = number of sectors in bank. address: 58h = bank a; 59h = bank b; 5ah = bank c; 5bh = bank d data: bds128h / bds640h
may 10, 2006 27024b3 am29bds128h/am29bds640h 27 data sheet table 12. am29bds128h sector address table bank sector sector size (x16) address range bank sector sector size (x16) address range bank d sa0 4 kwords 000000h?000fffh bank c sa39 32 kwords 100000h?107fffh sa1 4 kwords 001000h?001fffh sa40 32 kwords 108000h?10ffffh sa2 4 kwords 002000h?002fffh sa41 32 kwords 110000h?117fffh sa3 4 kwords 003000h?003fffh sa42 32 kwords 118000h?11ffffh sa4 4 kwords 004000h?004fffh sa43 32 kwords 120000h?127fffh sa5 4 kwords 005000h?005fffh sa44 32 kwords 128000h?12ffffh sa6 4 kwords 006000h?006fffh sa45 32 kwords 130000h?137fffh sa7 4 kwords 007000h?007fffh sa46 32 kwords 138000h?13ffffh sa8 32 kwords 008000h?00ffffh sa47 32 kwords 140000h?147fffh sa9 32 kwords 010000h?017fffh sa48 32 kwords 148000h?14ffffh sa10 32 kwords 018000h?01ffffh sa49 32 kwords 150000h?157fffh sa11 32 kwords 020000h?027fffh sa50 32 kwords 158000h?15ffffh sa12 32 kwords 028000h?02ffffh sa51 32 kwords 160000h?167fffh sa13 32 kwords 030000h?037fffh sa52 32 kwords 168000h?16ffffh sa14 32 kwords 038000h?03ffffh sa53 32 kwords 170000h?177fffh sa15 32 kwords 040000h?047fffh sa54 32 kwords 178000h?17ffffh sa16 32 kwords 048000h?04ffffh sa55 32 kwords 180000h?187fffh sa17 32 kwords 050000h?057fffh sa56 32 kwords 188000h?18ffffh sa18 32 kwords 058000h?05ffffh sa57 32 kwords 190000h?197fffh sa19 32 kwords 060000h?067fffh sa58 32 kwords 198000h?19ffffh sa20 32 kwords 068000h?06ffffh sa59 32 kwords 1a0000h?1a7fffh sa21 32 kwords 070000h?077fffh sa60 32 kwords 1a8000h?1affffh sa22 32 kwords 078000h?07ffffh sa61 32 kwords 1b0000h?1b7fffh sa23 32 kwords 080000h?087fffh sa62 32 kwords 1b8000h?1bffffh sa24 32 kwords 088000h?08ffffh sa63 32 kwords 1c0000h?1c7fffh sa25 32 kwords 090000h?097fffh sa64 32 kwords 1c8000h?1cffffh sa26 32 kwords 098000h?09ffffh sa65 32 kwords 1d0000h?1d7fffh sa27 32 kwords 0a0000h?0a7fffh sa66 32 kwords 1d8000h?1dffffh sa28 32 kwords 0a8000h?0affffh sa67 32 kwords 1e0000h?1e7fffh sa29 32 kwords 0b0000h?0b7fffh sa68 32 kwords 1e8000h?1effffh sa30 32 kwords 0b8000h?0bffffh sa69 32 kwords 1f0000h?1f7fffh sa31 32 kwords 0c0000h?0c7fffh sa70 32 kwords 1f8000h?1fffffh sa32 32 kwords 0c8000h?0cffffh sa33 32 kwords 0d0000h?0d7fffh sa34 32 kwords 0d8000h?0dffffh sa35 32 kwords 0e0000h?0e7fffh sa36 32 kwords 0e8000h?0effffh sa37 32 kwords 0f0000h?0f7fffh sa38 32 kwords 0f8000h?0fffffh
28 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet bank c sa71 32 kwords 200000h?207fffh bank c sa103 32 kwords 300000h?307fffh sa72 32 kwords 208000h?20ffffh sa104 32 kwords 308000h?30ffffh sa73 32 kwords 210000h?217fffh sa105 32 kwords 310000h?317fffh sa74 32 kwords 218000h?21ffffh sa106 32 kwords 318000h?31ffffh sa75 32 kwords 220000h?227fffh sa107 32 kwords 320000h?327fffh sa76 32 kwords 228000h?22ffffh sa108 32 kwords 328000h?32ffffh sa77 32 kwords 230000h?237fffh sa109 32 kwords 330000h?337fffh sa78 32 kwords 238000h?23ffffh sa110 32 kwords 338000h?33ffffh sa79 32 kwords 240000h?247fffh sa111 32 kwords 340000h?347fffh sa80 32 kwords 248000h?24ffffh sa112 32 kwords 348000h?34ffffh sa81 32 kwords 250000h?257fffh sa113 32 kwords 350000h?357fffh sa82 32 kwords 258000h?25ffffh sa114 32 kwords 358000h?35ffffh sa83 32 kwords 260000h?267fffh sa115 32 kwords 360000h?367fffh sa84 32 kwords 268000h?26ffffh sa116 32 kwords 368000h?36ffffh sa85 32 kwords 270000h?277fffh sa117 32 kwords 370000h?377fffh sa86 32 kwords 278000h?27ffffh sa118 32 kwords 378000h?37ffffh sa87 32 kwords 280000h?287fffh sa119 32 kwords 380000h?387fffh sa88 32 kwords 288000h?28ffffh sa120 32 kwords 388000h?38ffffh sa89 32 kwords 290000h?297fffh sa121 32 kwords 390000h?397fffh sa90 32 kwords 298000h?29ffffh sa122 32 kwords 398000h?39ffffh sa91 32 kwords 2a0000h?2a7fffh sa123 32 kwords 3a0000h?3a7fffh sa92 32 kwords 2a8000h?2affffh sa124 32 kwords 3a8000h?3affffh sa93 32 kwords 2b0000h?2b7fffh sa125 32 kwords 3b0000h?3b7fffh sa94 32 kwords 2b8000h?2bffffh sa126 32 kwords 3b8000h?3bffffh sa95 32 kwords 2c0000h?2c7fffh sa127 32 kwords 3c0000h?3c7fffh sa96 32 kwords 2c8000h?2cffffh sa128 32 kwords 3c8000h?3cffffh sa97 32 kwords 2d0000h?2d7fffh sa129 32 kwords 3d0000h?3d7fffh sa98 32 kwords 2d8000h?2dffffh sa130 32 kwords 3d8000h?3dffffh sa99 32 kwords 2e0000h?2e7fffh sa131 32 kwords 3e0000h?3e7fffh sa100 32 kwords 2e8000h?2effffh sa132 32 kwords 3e8000h?3effffh sa101 32 kwords 2f0000h?2f7fffh s a133 32 kwords 3f0000h?3f7fffh sa102 32 kwords 2f8000h?2fffffh s a134 32 kwords 3f8000h?3fffffh table 12. am29bds128h sector address table (continued) bank sector sector size (x16) address range bank sector sector size (x16) address range
may 10, 2006 27024b3 am29bds128h/am29bds640h 29 data sheet bank b sa135 32 kwords 400000h?407fffh bank b sa167 32 kwords 500000h?507fffh sa136 32 kwords 408000h?40ffffh sa168 32 kwords 508000h?50ffffh sa137 32 kwords 410000h?417fffh sa169 32 kwords 510000h?517fffh sa138 32 kwords 418000h?41ffffh sa170 32 kwords 518000h?51ffffh sa139 32 kwords 420000h?427fffh sa171 32 kwords 520000h?527fffh sa140 32 kwords 428000h?42ffffh sa172 32 kwords 528000h?52ffffh sa141 32 kwords 430000h?437fffh sa173 32 kwords 530000h?537fffh sa142 32 kwords 438000h?43ffffh sa174 32 kwords 538000h?53ffffh sa143 32 kwords 440000h?447fffh sa175 32 kwords 540000h?547fffh sa144 32 kwords 448000h?44ffffh sa176 32 kwords 548000h?54ffffh sa145 32 kwords 450000h?457fffh sa177 32 kwords 550000h?557fffh sa146 32 kwords 458000h?45ffffh sa178 32 kwords 558000h?55ffffh sa147 32 kwords 460000h?467fffh sa179 32 kwords 560000h?567fffh sa148 32 kwords 468000h?46ffffh sa180 32 kwords 568000h?56ffffh sa149 32 kwords 470000h?477fffh sa181 32 kwords 570000h?577fffh sa150 32 kwords 478000h?47ffffh sa182 32 kwords 578000h?57ffffh sa151 32 kwords 480000h?487fffh sa183 32 kwords 580000h?587fffh sa152 32 kwords 488000h?48ffffh sa184 32 kwords 588000h?58ffffh sa153 32 kwords 490000h?497fffh sa185 32 kwords 590000h?597fffh sa154 32 kwords 498000h?49ffffh sa186 32 kwords 598000h?59ffffh sa155 32 kwords 4a0000h?4a7fffh sa187 32 kwords 5a0000h?5a7fffh sa156 32 kwords 4a8000h?4affffh sa188 32 kwords 5a8000h?5affffh sa157 32 kwords 4b0000h?4b7fffh sa189 32 kwords 5b0000h?5b7fffh sa158 32 kwords 4b8000h?4bffffh sa190 32 kwords 5b8000h?5bffffh sa159 32 kwords 4c0000h?4c7fffh sa191 32 kwords 5c0000h?5c7fffh sa160 32 kwords 4c8000h?4cffffh sa192 32 kwords 5c8000h?5cffffh sa161 32 kwords 4d0000h?4d7fffh sa193 32 kwords 5d0000h?5d7fffh sa162 32 kwords 4d8000h?4dffffh sa194 32 kwords 5d8000h?5dffffh sa163 32 kwords 4e0000h?4e7fffh sa195 32 kwords 5e0000h?5e7fffh sa164 32 kwords 4e8000h?4effffh sa196 32 kwords 5e8000h?5effffh sa165 32 kwords 4f0000h?4f7fffh s a197 32 kwords 5f0000h?5f7fffh sa166 32 kwords 4f8000h?4fffffh s a198 32 kwords 5f8000h?5fffffh table 12. am29bds128h sector address table (continued) bank sector sector size (x16) address range bank sector sector size (x16) address range
30 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet bank b sa199 32 kwords 600000h?607fffh bank a sa231 32 kwords 700000h?707fffh sa200 32 kwords 608000h?60ffffh sa232 32 kwords 708000h?70ffffh sa201 32 kwords 610000h?617fffh sa233 32 kwords 710000h?717fffh sa202 32 kwords 618000h?61ffffh sa234 32 kwords 718000h?71ffffh sa203 32 kwords 620000h?627fffh sa235 32 kwords 720000h?727fffh sa204 32 kwords 628000h?62ffffh sa236 32 kwords 728000h?72ffffh sa205 32 kwords 630000h?637fffh sa237 32 kwords 730000h?737fffh sa206 32 kwords 638000h?63ffffh sa238 32 kwords 738000h?73ffffh sa207 32 kwords 640000h?647fffh sa239 32 kwords 740000h?747fffh sa208 32 kwords 648000h?64ffffh sa240 32 kwords 748000h?74ffffh sa209 32 kwords 650000h?657fffh sa241 32 kwords 750000h?757fffh sa210 32 kwords 658000h?65ffffh sa242 32 kwords 758000h?75ffffh sa211 32 kwords 660000h?667fffh sa243 32 kwords 760000h?767fffh sa212 32 kwords 668000h?66ffffh sa244 32 kwords 768000h?76ffffh sa213 32 kwords 670000h?677fffh sa245 32 kwords 770000h?777fffh sa214 32 kwords 678000h?67ffffh sa246 32 kwords 778000h?77ffffh sa215 32 kwords 680000h?687fffh sa247 32 kwords 780000h?787fffh sa216 32 kwords 688000h?68ffffh sa248 32 kwords 788000h?78ffffh sa217 32 kwords 690000h?697fffh sa249 32 kwords 790000h?797fffh sa218 32 kwords 698000h?69ffffh sa250 32 kwords 798000h?79ffffh sa219 32 kwords 6a0000h?6a7fffh sa251 32 kwords 7a0000h?7a7fffh sa220 32 kwords 6a8000h?6affffh sa252 32 kwords 7a8000h?7affffh sa221 32 kwords 6b0000h?6b7fffh sa253 32 kwords 7b0000h?7b7fffh sa222 32 kwords 6b8000h?6bffffh sa254 32 kwords 7b8000h?7bffffh sa223 32 kwords 6c0000h?6c7fffh sa255 32 kwords 7c0000h?7c7fffh sa224 32 kwords 6c8000h?6cffffh sa256 32 kwords 7c8000h?7cffffh sa225 32 kwords 6d0000h?6d7fffh sa257 32 kwords 7d0000h?7d7fffh sa226 32 kwords 6d8000h?6dffffh sa258 32 kwords 7d8000h?7dffffh sa227 32 kwords 6e0000h?6e7fffh sa259 32 kwords 7e0000h?7e7fffh sa228 32 kwords 6e8000h?6effffh sa260 32 kwords 7e8000h?7effffh sa229 32 kwords 6f0000h?6f7fffh s a261 32 kwords 7f0000h?7f7fffh sa230 32 kwords 6f8000h?6fffffh s a262 4 kwords 7f8000h?7f8fffh sa263 4 kwords 7f9000h?7f9fffh sa264 4 kwords 7fa000h?7fafffh sa265 4 kwords 7fb000h?7fbfffh sa266 4 kwords 7fc000h?7fcfffh sa267 4 kwords 7fd000h?7fdfffh sa268 4 kwords 7fe000h?7fefffh sa269 4 kwords 7ff000h?7fffffh table 12. am29bds128h sector address table (continued) bank sector sector size (x16) address range bank sector sector size (x16) address range
may 10, 2006 27024b3 am29bds128h/am29bds640h 31 data sheet table 13. am29bds640h sector address table bank sector sector size address range bank sector sector size address range bank d sa0 4 kwords 000000h?000fffh bank c sa36 32 kwords 0e8000h?0effffh sa1 4 kwords 001000h?001fffh sa37 32 kwords 0f0000h?0f7fffh sa2 4 kwords 002000h?002fffh sa38 32 kwords 0f8000h?0fffffh sa3 4 kwords 003000h?003fffh sa39 32 kwords 100000h?107fffh sa4 4 kwords 004000h?004fffh sa40 32 kwords 108000h?10ffffh sa5 4 kwords 005000h?005fffh sa41 32 kwords 110000h?117fffh sa6 4 kwords 006000h?006fffh sa42 32 kwords 118000h?11ffffh sa7 4 kwords 007000h?007fffh sa43 32 kwords 120000h?127fffh sa8 32 kwords 008000h?00ffffh sa44 32 kwords 128000h?12ffffh sa9 32 kwords 010000h?017fffh sa45 32 kwords 130000h?137fffh sa10 32 kwords 018000h?01ffffh sa46 32 kwords 138000h?13ffffh sa11 32 kwords 020000h?027fffh sa47 32 kwords 140000h?147fffh sa12 32 kwords 028000h?02ffffh sa48 32 kwords 148000h?14ffffh sa13 32 kwords 030000h?037fffh sa49 32 kwords 150000h?157fffh sa14 32 kwords 038000h?03ffffh sa50 32 kwords 158000h?15ffffh sa15 32 kwords 040000h?047fffh sa51 32 kwords 160000h?167fffh sa16 32 kwords 048000h?04ffffh sa52 32 kwords 168000h?16ffffh sa17 32 kwords 050000h?057fffh sa53 32 kwords 170000h?177fffh sa18 32 kwords 058000h?05ffffh sa54 32 kwords 178000h?17ffffh sa19 32 kwords 060000h?067fffh sa55 32 kwords 180000h?187fffh sa20 32 kwords 068000h?06ffffh sa56 32 kwords 188000h?18ffffh sa21 32 kwords 070000h?077fffh sa57 32 kwords 190000h?197fffh sa22 32 kwords 078000h?07ffffh sa58 32 kwords 198000h?19ffffh bank c sa23 32 kwords 080000h?087fffh sa59 32 kwords 1a0000h?1a7fffh sa24 32 kwords 088000h?08ffffh sa60 32 kwords 1a8000h?1affffh sa25 32 kwords 090000h?097fffh sa61 32 kwords 1b0000h?1b7fffh sa26 32 kwords 098000h?09ffffh sa62 32 kwords 1b8000h?1bffffh sa27 32 kwords 0a0000h?0a7fffh sa63 32 kwords 1c0000h?1c7fffh sa28 32 kwords 0a8000h?0affffh sa64 32 kwords 1c8000h?1cffffh sa29 32 kwords 0b0000h?0b7fffh sa65 32 kwords 1d0000h?1d7fffh sa30 32 kwords 0b8000h?0bffffh sa66 32 kwords 1d8000h?1dffffh sa31 32 kwords 0c0000h?0c7fffh sa67 32 kwords 1e0000h?1e7fffh sa32 32 kwords 0c8000h?0cffffh sa68 32 kwords 1e8000h?1effffh sa33 32 kwords 0d0000h?0d7fffh sa69 32 kwords 1f0000h?1f7fffh sa34 32 kwords 0d8000h?0dffffh sa70 32 kwords 1f8000h?1fffffh sa35 32 kwords 0e0000h?0e7fffh
32 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet bank b sa71 32 kwords 200000h?207fffh bank b sa107 32 kwords 320000h?327fffh sa72 32 kwords 208000h?20ffffh sa108 32 kwords 328000h?32ffffh sa73 32 kwords 210000h?217fffh sa1 09 32 kwords 330000h?337fffh sa74 32 kwords 218000h?21ffffh sa110 32 kwords 338000h?33ffffh sa75 32 kwords 220000h?227fffh sa1 11 32 kwords 340000h?347fffh sa76 32 kwords 228000h?22ffffh sa112 32 kwords 348000h?34ffffh sa77 32 kwords 230000h?237fffh sa1 13 32 kwords 350000h?357fffh sa78 32 kwords 238000h?23ffffh sa114 32 kwords 358000h?35ffffh sa79 32 kwords 240000h?247fffh sa1 15 32 kwords 360000h?367fffh sa80 32 kwords 248000h?24ffffh sa116 32 kwords 368000h?36ffffh sa81 32 kwords 250000h?257fffh sa1 17 32 kwords 370000h?377fffh sa82 32 kwords 258000h?25ffffh sa118 32 kwords 378000h?37ffffh sa83 32 kwords 260000h?267fffh bank a sa119 32 kwords 380000h?387fffh sa84 32 kwords 268000h?26ffffh sa120 32 kwords 388000h?38ffffh sa85 32 kwords 270000h?277fffh sa1 21 32 kwords 390000h?397fffh sa86 32 kwords 278000h?27ffffh sa122 32 kwords 398000h?39ffffh sa87 32 kwords 280000h?287fffh sa123 32 kwords 3a0000h?3a7fffh sa88 32 kwords 288000h?28ffffh sa124 32 kwords 3a8000h?3affffh sa89 32 kwords 290000h?297fffh sa125 32 kwords 3b0000h?3b7fffh sa90 32 kwords 298000h?29ffffh sa126 32 kwords 3b8000h?3bffffh sa91 32 kwords 2a0000h?2a7fffh sa127 32 kwords 3c0000h?3c7fffh sa92 32 kwords 2a8000h?2affffh sa128 32 kwords 3c8000h?3cffffh sa93 32 kwords 2b0000h?2b7fffh sa129 32 kwords 3d0000h?3d7fffh sa94 32 kwords 2b8000h?2bffffh sa130 32 kwords 3d8000h?3dffffh sa95 32 kwords 2c0000h?2c7fffh sa131 32 kwords 3e0000h?3e7fffh sa96 32 kwords 2c8000h?2cffffh sa132 32 kwords 3e8000h?3effffh sa97 32 kwords 2d0000h?2d7fffh sa133 32 kwords 3f0000h?3f7fffh sa98 32 kwords 2d8000h?2dffffh sa134 4 kwords 3f8000h?3f8fffh sa99 32 kwords 2e0000h?2e7fffh sa135 4 kwords 3f9000h?3f9fffh sa100 32 kwords 2e8000h?2effffh sa136 4 kwords 3fa000h?3fafffh sa101 32 kwords 2f0000h?2f7fffh sa137 4 kwords 3fb000h?3fbfffh sa102 32 kwords 2f8000h?2fffffh sa138 4 kwords 3fc000h?3fcfffh sa103 32 kwords 300000h?307fffh sa139 4 kwords 3fd000h?3fdfffh sa104 32 kwords 308000h?30ffffh sa140 4 kwords 3fe000h?3fefffh sa105 32 kwords 310000h?317fffh sa141 4 kwords 3ff000h?3fffffh sa106 32 kwords 318000h?31ffffh table 13. am29bds640h sector address table bank sector sector size address range bank sector sector size address range
may 10, 2006 27024b3 am29bds128h/am29bds640h 33 data sheet command definitions writing specific address and data commands or sequences into the command register initiates device operations. table 20, ?memory array command defini- tions,? on page 46 defines the valid register command sequences. writing incorrect address and data values or writing them in the improper sequence may place the device in an unknown state. the system must write the reset command to return the device to reading array data. refer to the ac characteristics section for timing diagrams. reading array data the device is automatically set to reading array data after device power-up. no commands are required to retrieve data in asynchronous mode. each bank is ready to read array data after completing an embedded program or embedded erase algorithm. after the device accepts an erase suspend command, the corresponding bank enters the erase-sus- pend-read mode, after which the system can read data from any non-erase-suspended sector within the same bank. after completing a programming operation in the erase suspend mode, the system may once again read array data from any non-erase-suspended sector within the same bank. see the ?erase suspend/erase resume commands? section on page 39 for more information. the system must issue the reset command to return a bank to the read (or erase-suspend-read) mode if dq5 goes high during an active program or erase operation, or if the bank is in the autoselect mode. see the ?reset command? section on page 36 for more information. see also ?requirements for asynchronous read oper- ation (non-burst)? section on page 11 and ?require- ments for synchronous (burst) read operation? section on page 11 for more information. the asyn- chronous read and synchronous/burst read tables provide the read parameters, and figure 16, ?clk syn- chronous burst mode read (rising active clk),? on page 58 , figure 18, ?synchronous burst mode read,? on page 59 , and figure 31, ?asynchronous mode read with latched addresses,? on page 67 show the timings. set configuration r egister command se- quence the device uses a configuration register to set the various burst parameters: number of wait states, burst read mode, active clock edge, rdy configuration, and synchronous mode active. the configuration register must be set before the devi ce will enter burst mode. the configuration register is loaded with a three-cycle command sequence. the first two cycles are standard unlock sequences. on the third cycle, the data should be c0h, address bits a11?a0 should be 555h, and address bits a19?a12 set the code to be latched. the device will power up or afte r a hardware reset with the default setting, which is in asynchronous mode. the register must be set before the device can enter syn- chronous mode. the configuration register can not be changed during device operations (program, erase, or sector lock). figure 3. synchronous/asynchronous state diagram read mode setting on power-up or hardware reset, the device is set to be in asynchronous read mode. this setting allows the system to enable or disa ble burst mode during system operations. address a19 determines this setting: ?1? for asynchronous mode, ?0? for synchronous mode. programmable wait state configuration the programmable wait state feature informs the device of the number of clock cycles that must elapse after avd# is driven active be fore data will be available. this value is determined by the input frequency of the device. address bits a14?a12 determine the setting (see table 14, ?programmable wait state settings,? on page 34 ). the wait state command sequence instructs the device to set a particular number of clock cycles for the initial access in burst mode. the number of wait states that should be programmed into the device is directly related to the clock frequency. power-up/ hardware reset asynchronous read mode only synchronous read mode only set burst mode configuration register command for synchronous mode (d15 = 0) set burst mode configuration register command for asynchronous mode (d15 = 1)
34 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet table 14. programmable wait state settings notes: 1. upon power-up or hardware reset, the default setting is seven wait states. 2. rdy will default to being active with data when the wait state setting is set to a to tal initial access cycle of 2. it is recommended that the wait state command sequence be written, even if the default wait state value is desired, to ensure the device is set as expected. a hardware reset will set the wait state to the default set- ting. reduced wait-state handshaking option if the device is equipped with the reduced wait-state handshaking option, the host system should set address bits a14?a12 to 010 for the system/device to execute at maximum speed. ta b l e 1 5 describes the typical number of clock cycles (wait states) for various conditions. table 15. wait states for reduced wait-state handshaking notes: 1. if the latched address is 3eh or 3fh (or an address offset from either address by a multiple of 64), add two access cycles to the values listed. 2. in the 8-, 16-, and 32-word burst modes, the address pointer does not cross 64-word boundaries (3fh, or addresses offset from 3f h by a multiple of 64). 3. typical initial access cycles may vary depending on system margin requirements. a14 a13 a12 total initial access cycles 000 2 001 3 010 4 011 5 100 6 1 0 1 7 (default) 110 reserved 111 reserved system frequency range even initial address odd initial address device speed rating 6 ? 22 mhz 2 2 d (54 mhz) 22 ? 28 mhz 2 3 28 ? 43 mhz 3 4 43 ? 54 mhz 4 5 6 ? 28 mhz 2 2 e (66 mhz) 28 ? 35 mhz 2 3 35 ? 53 mhz 3 4 53 ? 66 mhz 4 5
may 10, 2006 27024b3 am29bds128h/am29bds640h 35 data sheet standard handshaking option for optimal burst mode performance on devices with the standard handshaking option, the host system must set the appropriate number of wait states in the flash device depending on the clock frequency. table 16 describes the typical number of clock cycles (wait states) for various conditions with a14-a12 set to 101. table 16. wait states for standard handshaking * in the 8-, 16- and 32-word burst read modes, the address pointer does not cross 64-word boundaries (addresses which are multiples of 3fh). the autoselect function allows the host system to determine whether the flash device is enabled for handshaking. see the ?autoselect command sequence? section on page 36 for more information. read mode configuration the device supports four different read modes: contin- uous mode, and 8, 16, and 32 word linear wrap around modes. a continuous sequence begins at the starting address and advances the address pointer until the burst operation is complete. if the highest address in the device is reached during the continuous burst read mode, the address pointer wraps around to the lowest address. for example, an eight-word linear read with wrap around begins on the starting address written to the device and then advances to the next 8 word boundary. the address pointer then returns to the 1st word after the previous eight word boundary, wrapping through the starting location. the sixteen- and thirty-two linear wrap around modes operate in a fashion similar to the eight-word mode. table 17 shows the address bits and settings for the four read modes. table 17. read mode settings note: upon power-up or hardware reset the default setting is continuous. burst active clock edge configuration by default, the device will deliver data on the rising edge of the clock after the initial synchronous access time. subsequent outputs will also be on the following rising edges, barring any delays. the device can be set so that the falling clock edge is active for all synchro- nous accesses. address bit a17 determines this set- ting; ?1? for rising active, ?0? for falling active. rdy configuration by default, the device is set so that the rdy pin will output v oh whenever there is valid data on the outputs. the device can be set so that rdy goes active one data cycle before active data. address bit a18 deter- mines this setting; ?1? for rdy active with data, ?0? for rdy active one clock cycle before valid data. in asyn- chronous mode, rdy is an open-drain output. configuration register table 18 shows the address bits that determine the configuration register settings for various device func- tions. conditions at address typical no. of clock cycles after avd# low initial address 7 initial address is 3e or 3fh (or offset from these addresses by a multiple of 64) and is at boundary crossing* 7 burst modes address bits a16 a15 continuous 0 0 8-word linear wrap around 0 1 16-word linear wrap around 1 0 32-word linear wrap around 1 1
36 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet table 18. configuration register note: device will be in the default state upon power-up or hardware reset. reset command writing the reset command resets the banks to the read or erase-suspend-read mode. address bits are don?t cares for this command. the reset command may be written between the sequence cycles in an erase command sequence before erasing begins. this resets the bank to which the system was writing to the read mode. once erasure begins, however, the device ignores reset commands until the operation is complete. the reset command may be written between the sequence cycles in a program command sequence before programming begins (prior to the third cycle). this resets the bank to which the system was writing to the read mode. if the program command sequence is written to a bank that is in the erase suspend mode, writing the reset command returns that bank to the erase-suspend-read mode. once programming begins, however, the device ignores reset commands until the operation is complete. the reset command may be written between the sequence cycles in an autoselect command sequence. once in the autoselect mode, the reset command must be written to return to the read mode. if a bank entered the autoselect mode while in the erase suspend mode, writing the reset command returns that bank to the erase-suspend-read mode. if dq5 goes high during a program or erase operation, writing the reset command returns the banks to the read mode (or erase-suspend-read mode if that bank was in erase suspend). autoselect command sequence the autoselect command sequence allows the host system to access the manufacturer and device codes, and determine whether or not a sector is protected. table 20, ?memory array command definitions,? on page 46 shows the address and data requirements. the autoselect command sequence may be written to an address within a bank that is either in the read or erase-suspend-read mode. the autoselect command may not be written while the device is actively program- ming or erasing in the other bank. the autoselect command sequence is initiated by first writing two unlock cycles. th is is followed by a third write cycle that contains the bank address and the autoselect command. the bank then enters the autoselect mode. no su bsequent data will be made available if the autoselect data is read in synchronous mode. the system may read at any address within the same bank any number of times without initiating another autoselect command sequence. read com- mands to other banks will retu rn data from the array. the following table describes the address require- ments for the various autoselect functions, and the resulting data. ba represents the bank address, and address bit function settings (binary) a19 set device read mode 0 = synchronous read (burst mode) enabled 1 = asynchronous mode (default) a18 rdy 0 = rdy active one clock cycle before data 1 = rdy active with data (default) a17 clock 0 = burst starts and data is out put on the falling edge of clk 1 = burst starts and data is output on the rising edge of clk (default) a16 a15 read mode synchronous mode 00 = continuous (default) 01 = 8-word linear with wrap around 10 = 16-word linear with wrap around 11 = 32-word linear with wrap around a14 a13 a12 programmable wait state 000 = data is valid on the 2th active clk edge after avd# transition to v ih 001 = data is valid on the 3th active clk edge after avd# transition to v ih 010 = data is valid on the 4th active clk edge after avd# transition to v ih 011 = data is valid on the 5th active clk edge after avd# transition to v ih 100 = data is valid on the 6th active clk edge after avd# transition to v ih 101 = data is valid on the 7th active clk edge after avd# transition to v ih (default) 110 = reserved 111 = reserved
may 10, 2006 27024b3 am29bds128h/am29bds640h 37 data sheet sa represents the sector address. the device id is read in three cycles. the system must write the reset command to return to the read mode (or erase-suspend-read mode if the bank was previously in erase suspend). enter secsi? sector /exit secsi sector command sequence the secsi sector region provides a secured data area containing a random, eight word electronic serial num- ber (esn). the system can access the secsi sector region by issuing the thr ee-cycle enter secsi sector command sequence. the device continues to access the secsi sector region until the system issues the four-cycle exit secsi sector command sequence. the exit secsi sector command sequence returns the de- vice to normal operation. the secsi sector is not ac- cessible when the device is executing an embedded program or embedded erase algorithm. table 20, ?memory array command definitions,? on page 46 shows the address and data requirements for both command sequences. program command sequence programming is a four-bus-cycle operation. the program command sequence is initiated by writing two unlock write cycles, followed by the program set-up command. the program address and data are written next, which in turn initiate the embedded program algorithm. the system is not required to provide further controls or timings. the device automatically provides internally generated program pulses and verifies the programmed cell margin. table 20, ?memory array command definitions,? on page 46 shows the address and data requirements for the program command sequence. when the embedded program algorithm is complete, that bank then returns to the read mode and addresses are no longer latched. the system can determine the status of the program operation by monitoring dq7 or dq6/dq2. refer to the ?write operation status? section on page 48 for information on these status bits. any commands written to the device during the embedded program algorithm are ignored. note that a hardware reset immediately terminates the program operation. the program command sequence should be reinitiated once that bank has returned to the read mode, to ensure data integrity. programming is allowed in any sequence and across sector boundaries. a bit cannot be programmed from ?0? back to a ?1.? attempting to do so may cause that bank to set dq5 = 1, or cause the dq7 and dq6 status bit to indicate the operation was successful. however, a succeeding read will show th at the data is still ?0.? only erase operations can convert a ?0? to a ?1.? unlock bypass command sequence the unlock bypass feature allows the system to prima- rily program to a bank faster than using the standard program command sequence. the unlock bypass command sequence is initiated by first writing two unlock cycles. this is followed by a third write cycle containing the unlock bypass command, 20h. the device then enters the unlock bypass mode. a two-cycle unlock bypass program command sequence is all that is required to program in this mode. the first cycle in this sequence c ontains the unlock bypass program command, a0h; the second cycle contains the program address and data. additional data is pro- grammed in the same manner. this mode dispenses with the initial two unlock cycles required in the stan- dard program command sequence, resulting in faster total programming time. the host system may also ini- tiate the chip erase and sector erase sequences in the unlock bypass mode. the erase command sequences are four cycles in length instead of six cycles. ta b l e 2 0 , ?memory array command definitions,? on page 46 shows the requirements for the unlock bypass command sequences. the unlock bypass reset command is required to return to reading array data when the bank is in the unlock bypass mode. during the unlock bypass mode, only the read, unlock bypass program, unlock bypa ss sector erase, unlock bypass chip erase, and unlock bypass reset com- table 19. autoselect data description address read data manufacturer id (ba) + 00h 0001h device id, word 1 (ba) + 01h 227eh (bds128h) 221eh (bds640h) device id, word 2 (ba) + 0eh 2218h (bds128h) 2201h (bds640h) device id, word 3 (ba) + 0fh 2200h sector protection verification (sa) + 02h 0001h (locked), 0000h (unlocked) indicator bits (ba) + 03h dq15 - dq8 = 0 dq7: factory lock bit 1 = locked, 0 = not locked dq6: customer lock bit 1 = locked, 0 = not locked dq5: handshake bit 1 = reduced wait-state handshake, 0 = standard handshake
38 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet mands are valid. to exit the unlock bypass mode, the system must issue the tw o-cycle unlock bypass reset command sequence. the first cycle must contain the bank address and the data 90h. the second cycle need only contain the data 00h. the bank then returns to the read mode. the device offers accelerated program operations through the acc input. when the system asserts v hh on this input, the device automatically enters the unlock bypass mode. the system may then write the two-cycle unlock bypass program command sequence. the device uses the higher voltage on the acc input to accelerate the operation. figure 4, ?program operation,? on page 38 illustrates the algorithm for the program operation. refer to the erase/program operations table in the ac character- istics section for parameters, and figure 34, ?asyn- chronous program operation timings: avd# latched addresses,? on page 70 and figure 36, ?synchronous program operation timings: we# latched addresses,? on page 72 for timing diagrams. figure 4. program operation chip erase command sequence chip erase is a six bus cycle operation. the chip erase command sequence is initiated by writing two unlock cycles, followed by a set-up command. two additional unlock write cycles are then followed by the chip erase command, which in turn invokes the embedded erase algorithm. the device does not require the system to preprogram prior to erase. the embedded erase algo- rithm automatically preprograms and verifies the entire memory for an all zero data pattern prior to electrical erase. the system is not required to provide any con- trols or timings during these operations. ta bl e 2 0 , ?memory array command definitions,? on page 46 shows the address and data requirements for the chip erase command sequence. when the embedded erase algorithm is complete, that bank returns to the read mode and addresses are no longer latched. the system can determine the status of the erase operation by using dq7 or dq6/dq2. refer to the ?write operation status? section on page 48 for information on these status bits. any commands written during the chip erase operation are ignored. however, note that a hardware reset immediately terminates the erase operation. if that occurs, the chip erase command sequence should be reinitiated once that bank has returned to reading array data, to ensure data integrity. the host system may also initiate the chip erase command sequence while the device is in the unlock bypass mode. the command sequence is two cycles cycles in length instead of six cycles. see table 20, ?memory array command definitions,? on page 46 for details on the unlock bypass command sequences. figure 5, ?erase operation,? on page 40 illustrates the algorithm for the erase operation. refer to the erase/program operations table in the ac character- istics section for parameters and timing diagrams. sector erase command sequence sector erase is a six bus cycle operation. the sector erase command sequence is initiated by writing two unlock cycles, followed by a set-up command. two additional unlock cycles are written, and are then fol- lowed by the address of the sector to be erased, and the sector erase command. table 20, ?memory array command definitions,? on page 46 shows the address and data requirements for the sector erase command sequence. the device does not requir e the system to preprogram prior to erase. the embedded erase algorithm auto- matically programs and verifies the entire memory for an all zero data pattern prior to electrical erase. the system is not required to provide any controls or timings during these operations. after the command sequence is written, a sector erase time-out of no less than t sea occurs. during the time-out period, additional sector addresses and sector erase commands may be written. loading the sector erase buffer may be done in any sequence, and the start write program command sequence data poll from system verify data? no yes last address? no yes programming completed increment address embedded program algorithm in progress note: see table 20 for program command sequence.
may 10, 2006 27024b3 am29bds128h/am29bds640h 39 data sheet number of sectors may be from one sector to all sec- tors. the time between these additional cycles must be less than t sea , otherwise erasure may begin. any sector erase address and command following the exceeded time-out, t sea, may or may not be accepted. it is recommended that processor interrupts be dis- abled during this time to ensure all commands are accepted. the interrupts can be re-enabled after the last sector erase command is written. any command other than sector erase or erase suspend during the time-out period resets that bank to the read mode. the system must rewrite the command sequence and any additional addresses and commands. the system can monitor dq3 to determine if the sector erase timer has timed out (see ?dq3: sector erase timer? section on page 51 .) the time-out begins from the rising edge of the final we# pulse in the command sequence. when the embedded erase algorithm is complete, the bank returns to reading array data and addresses are no longer latched. note that while the embedded erase operation is in progress, the system can read data from the non-erasing bank. the system can determine the status of the erase operation by reading dq7 or dq6/dq2 in the erasing bank. refer to the ?write operation status? section on page 48 for information on these status bits. once the sector erase operation has begun, only the erase suspend command is valid. all other commands are ignored. however, note that a hardware reset immediately terminates the erase operation. if that occurs, the sector erase command sequence should be reinitiated once that bank has returned to reading array data, to ensure data integrity. the host system may also initiate the sector erase command sequence while the device is in the unlock bypass mode. the command sequence is four cycles cycles in length instead of six cycles. the unlock bypass reset command is required to return to reading array data when the bank is in the unlock bypass mode. figure 5, ?erase operation,? on page 40 illustrates the algorithm for the erase operation. refer to the erase/program operations table in the figure , ?ac characteristics,? on page 69 for parameters and timing diagrams. erase suspend/erase resume commands the erase suspend command, b0h, allows the system to interrupt a sector erase operation and then read data from, or program data to, any sector not selected for erasure. the bank address is required when writing this command. this command is valid only during the sector erase operation, including the minimum t sea time-out period during the sector erase command sequence. the erase suspend command is ignored if written during the chip erase operation or embedded program algorithm. when the erase suspend command is written during the sector erase operation, the device requires a maximum of t esl to suspend the erase operation. how- ever, when the erase suspend command is written during the sector erase time-out, the device immedi- ately terminates the time-out period and suspends the erase operation. after the erase operation has been suspended, the bank enters the erase-suspend-read mode. the system can read data from or program data to any sector not selected for erasure. (the device ?erase sus- pends? all sectors selected for erasure.) reading at any address within erase-suspended sectors produces status information on dq7?dq0. the system can use dq7, or dq6 and dq2 together, to determine if a sector is actively erasing or is erase-suspended. refer to the figure , ?write operation status,? on page 48 for information on these status bits. after an erase-suspended program operation is com- plete, the bank returns to the erase-suspend-read mode. the system can determine the status of the program operation using the dq7 or dq6 status bits, just as in the standard program operation. refer to the ?write operation status? section on page 48 for more information. in the erase-suspend-read mode, the system can also issue the autoselect command sequence. refer to the ?autoselect mode? section on page 14 and ?autoselect command sequence? section on page 36 for details. to resume the sector erase operation, the system must write the erase resume command. the bank address of the erase-suspended bank is required when writing this command. further writes of the resume command
40 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet are ignored. another erase suspend command can be written after the chip has resumed erasing. figure 5. erase operation password program command the password program command permits program- ming the password that is used as part of the hard- ware protection scheme. the actual password is 64-bits long. 4 password program commands are re- quired to program the password. the user must enter the unlock cycle, password program command (38h) and the program address/data for each portion of the password when programming. there are no provisions for entering the 2-cycle unlock cycle, the password program command, and all the password data. there is no special addressing order required for program- ming the password. also, when the password is under- going programming, simultaneous operation is disabled. read operations to any memory location will return the programming status. once programming is complete, the user must issue a read/reset com- mand to return the device to normal operation. once the password is written and verified, the password mode locking bit must be set in order to prevent verifi- cation. the password program command is only ca- pable of programming ?0?s. programming a ?1? after a cell is programmed as a ?0? results in a time-out by the embedded program algorithm? with the cell remain- ing as a ?0?. the password is all fs when shipped from the factory. all 64-bit password combinations are valid as a password. password verify command the password verify command is used to verify the password. the password is verifiable only when the password mode locking bit is not programmed. if the password mode locking bit is programmed and the user attempts to verify the password, the device will al- ways drive all fs onto the dq data bus. also, the device will not operate in simultaneous oper- ation when the password verify command is executed. only the password is returned regardless of the bank address. the lower two address bits (a1?a0) are valid during the password verify. writing the secsi sector exit command returns the device back to normal oper- ation. password protection mode locking bit program command the password protection mode locking bit program command programs the password protection mode locking bit, which prevents further verifies or updates to the password. once programmed, the password protection mode locking bit cannot be erased and the persistent protection mode locking bit program cir- cuitry is disabled, thereby forcing the device to remain in the password protection mode. after issuing ?pl/68h? at the fourth bus cycle, the device requires a time out period of approximately 150 s for program- ming the password protection mode locking bit. then by writing ?pl/48h? at the fifth bus cycle, the device outputs verify data at dq0. if dq0 = 1, then the pass- word protection mode locking bit is programmed. if not, the system must repeat this program sequence from the fourth cycle of ?pl/68h?. exiting the password protection mode locking bit program command is ac- complished by writing the secsi sector exit command or read/reset command. persistent sector protection mode locking bit program command the persistent sector protection mode locking bit program command programs the persistent sector protection mode locking bit, which prevents the pass- word mode locking bit from ever being programmed. by disabling the program circuitry of the password mode locking bit, the device is forced to remain in the persistent sector protection mode of operation, once this bit is set. after issuing ?smpl/68h? at the fourth bus cycle, the device requires a time out period of ap- proximately 150 s for programming the persistent protection mode locking bit. then by writing ?smpl/48h? at the fifth bus cycle, the device outputs verify data at dq0. if dq0 = 1, then the persistent pro- start write erase command sequence data poll from system data = ffh? no yes erasure completed embedded erase algorithm in progress notes: 1. see table 20 for erase command sequence. 2. see the section on dq3 for information on the sector erase timer.
may 10, 2006 27024b3 am29bds128h/am29bds640h 41 data sheet tection mode locking bit is programmed. if not, the system must repeat this program sequence from the fourth cycle of ?pl/68h?. exiting the persistent protec- tion mode locking bit program command is accom- plished by writing the secsi sector exit command or reset command. secsi sector protection bit program command to protect the secsi sector, write the secsi sector protect command sequence while in the secsi sector mode. after issuing ?opbp/48h? at the fourth bus cy- cle, the device requires a time out period of approxi- mately 150 s to protect the secsi sector. then, by writing ?opbp/48? at the fifth bus cycle, the device out- puts verify data at dq0. if dq0 = 1, then the secsi sector is protected. if not, then the system must re- peat this program sequence from the fourth cycle of ?opbp/48h?. ppb lock bit set command the ppb lock bit set comman d is used to set the ppb lock bit if it is cleared either at reset or if the password unlock command was successfully exe- cuted. there is no ppb lock bit clear command. once the ppb lock bit is set, it cannot be cleared un- less the device is taken through a power-on clear or the password unlock command is executed. upon set- ting the ppb lock bit, the ppbs are latched into the dybs. if the password mode locking bit is set, the ppb lock bit status is reflected as set, even after a power-on reset cycle. exiting the ppb lock bit set command is accomplished by writing the secsi sector exit command, only while in the persistent sector pro- tection mode. dyb write command the dyb write command is used to set or clear a dyb for a given sector. the high order address bits (amax?a11) are issued at the same time as the code 01h or 00h on dq7-dq0. all other dq data bus pins are ignored during the data write cycle. the dybs are modifiable at any time, regardless of the state of the ppb or ppb lock bit. the dybs are cleared at power-up or hardware reset. exiting the dyb write command is accomplished by writing the read/reset command. password unlock command the password unlock command is used to clear the ppb lock bit so that the ppbs can be unlocked for modification, thereby allowi ng the ppbs to become ac- cessible for modification. the exact password must be entered in order for the unlocking function to occur. this command cannot be issued any faster than 2 s at a time to prevent a hacker from running through the all 64-bit combinations in an attempt to correctly match a password. if the command is issued before the 2 s execution window for each portion of the unlock, the command will be ignored. the password unlock function is accomplished by writing password unlock command and data to the de- vice to perform the clearing of the ppb lock bit. the password is 64 bits long, so the user must write the password unlock command 4 times. a1 and a0 are used for matching. writing the password unlock com- mand is not address order specific. the lower address a1?a0= 00, the next password unlock command is to a1?a0= 01, then to a1?a0= 10, and finally to a1?a0= 11. once the password unlock command is entered for all four words, the rdy pin goes low indicating that the device is busy. approximately 1 s is required for each portion of the unlock. once the first portion of the password unlock completes (rdy is not driven and dq6 does not toggle when read), the password un- lock command is issued again, only this time with the next part of the password. four password unlock com- mands are required to successfully clear the ppb lock bit. as with the first password unlock command, the rdy signal goes low and reading the device re- sults in the dq6 pin toggling on successive read oper- ations until complete. it is the responsibility of the microprocessor to keep track of the number of pass- word unlock commands, the order, and when to read the ppb lock bit to confirm successful password un- lock. in order to relock the device into the password mode, the ppb lock bit set command can be re-is- sued. exiting the password unlock command is ac- complished by writing secs i sector exit command.
42 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet figure 6. ppb program algorithm
may 10, 2006 27024b3 am29bds128h/am29bds640h 43 data sheet ppb program command the ppb program command is used to program, or set, a given ppb. each ppb is individually pro- grammed (but is bulk er ased with the other ppbs). the specific sector address (amax?a12) are written at the same time as the program command 60h. if the ppb lock bit is set and the correspondingly ppb is set for the sector, the ppb program command will not execute and the command will time out without pro- gramming the ppb. after issuing ?sba+wp/68h? at the fourth bus cycle, the device requires a time out pe- riod of approximately 150 s to program the ppb. writing ?sba+wp/48? at the fifth bus cycle produces verify data at dq0. if dq0 = 1, the ppb is pro- grammed. if not, the system must repeat this program sequence from the fourth cycle of ?sba+wp/68h?. the ppb program command does not follow the embedded program algorithm. writing the secsi sector exit command or read/reset command return the device back to normal operation. all ppb erase command the all ppb erase command is used to erase all ppbs in bulk. there is no means for individually eras- ing a specific ppb. unlike the ppb program, no spe- cific sector address is required. however, when the ppb erase command is writt en (60h), a ll sector ppbs are erased in parallel. if the ppb lock bit is set, the all ppb erase command will not execute and the command will time-out witho ut erasing the ppbs. after issuing ?wp/60h? at the fourth bus cycle, the device re- quires a time out period of approximately 1.5 ms to erase the ppb. writing ?sba+wp/40h? at the fifth bus cycle produces verify data at dq0. if dq0 = 0, the ppb is erased. if not, the sys tem must repeat this pro- gram sequence from the fourth cycle of ?wp/60h?. it is the responsibility of the system to preprogram all ppbs prior to issuing the all ppb erase command. if the system attempts to erase a cleared ppb, over-era- sure may occur, making it difficult to program the ppb at a later time. also note that the total number of ppb program/erase cycles is limited to 100 cycles. cycling the ppbs beyond 100 cycl es is not guaranteed. writing the secsi sector exit command or read/re- set command return the device to normal operation.
44 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet figure 7. ppb erase algorithm
may 10, 2006 27024b3 am29bds128h/am29bds640h 45 data sheet dyb write command the dyb write command is used for setting the dyb, which is a volatile bit that is cleared at hardware reset. there is one dyb per sector. if the ppb is set, the sec- tor is protected regardless of the value of the dyb. if the ppb is cleared, setting th e dyb to a 1 protects the sector from programs or erases. since this is a volatile bit, removing power or resetting the device will clear the dybs. writing read/reset command returns the device to normal operations. ppb status command the programming of the ppb for a given sector can be verified by writing a ppb st atus verify command to the device. writing read/reset command and secsi sec- tor exit command return the device to normal opera- tion. ppb lock bit st atus command the programming of the ppb lock bit for a given sec- tor can be verified by writing a ppb lock bit status ver- ify command to the device. read/reset and secsi sector exit return the device to normal operation. dyb status command the programming of the dyb for a given sector can be verified by writing a dyb status command to the de- vice. writing secsi sector exit command returns the device to normal operation.
46 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet command definitions table 20. memory array command definitions * for actual hexadecimal data values, refer to the note number indicated. legend: x = don?t care ra = address of the memory location to be read. rd = data read from location ra during read operation. pa = address of the memory location to be programmed. addresses latch on the rising edge of the avd# pulse or active edge of clk which ever comes first. pd = data to be programmed at location pa. data latches on the rising edge of we# or ce# pulse, whichever happens first. sa = address of the sector to be verified (in autoselect mode) or erased. address bits amax?a12 uniquely select any sector. ba = address of the bank (bds128h: a22?a20; bds640h: a21?a19) for which command is being written. sla = address of the sector to be locked. set sector address (sa) and either a6 = 1 for unlocked or a6 = 0 for locked. cr = configuration register address bits a19?a12. notes: 1. see table 1 for description of bus operations. 2. all values are in hexadecimal. 3. shaded cells indicate read cycles. all others are write cycles. 4. data bits dq15?dq8 are don?t care in command sequences, except for rd and pd. 5. unless otherwise noted, address bits amax?a12 are don?t cares. 6. writing incorrect address and data values or writing them in the improper sequence may place the device in an unknown state. the system must write the reset command to return the device to reading array data. 7. no unlock or command cycles required when bank is reading array data. 8. the reset command is required to return to reading array data (or to the erase-suspend-read mode if previously in erase suspend) when a bank is in the autoselect mode, or if dq5 goes high (while the bank is providing status information) or performing sector lock/unlock. 9. the fourth cycle of the autoselect command sequence is a read cycle. the system must provide the bank address. see the autoselect command sequence section for more information. 10. bds128h: 2218h; bds640h: 221eh. 11. bds128h: 2200h; bds640h: 2201h 12. the data is 0000h for an unlocked sector and 0001h for a locked sector 13. dq15?dq8 = 0, dq7: factory lock bit (1 = locked, 0 = not locked), dq6: customer lock bit (1 = locked, 0 = not locked), dq5: handshake bit (1 = reduced wait-state handshake, 0 = standard handshake), dq4?dq0 = 0 14. the unlock bypass command sequence is required prior to this command sequence. 15. the unlock bypass reset command is required to return to reading array data when the bank is in the unlock bypass mode. 16. the system may read and program in non-erasing sectors, or enter the autoselect mode, when in the erase suspend mode. the erase suspend command is valid only during a sector erase operation, and requires the bank address. 17. the erase resume command is valid only during the erase suspend mode, and requires the bank address. 18. see ?set configuration register command sequence? for details. this command is unavailable in unlock bypass mode. 19. command is valid when device is ready to read array data or when device is in autoselect mode. 20. the unlock bypass reset command is required to exit this mode before sending any other commands to the device. the only commands that are allowed in the unlock bypass mode are the entry and exit (reset), program, erase, sector erase and cfi. command sequence (notes) cycles bus cycles (notes 1?6) first second third fourth fifth sixth addr data addr data addr data addr data addr data addr data asynchronous read (7) 1 ra rd reset (8) 1 xxx f0 autoselect (9) manufacturer id 4 555 aa 2aa 55 ba+555 90 ba+x00 0001 device id (9, 10)* 6 555 aa 2aa 55 ba+555 90 ba+x01 227e ba+x0e (10)* ba+x0f (11)* sector lock verify (12)* 4 555 aa 2aa 55 sa+555 90 sa+x02 (12)* indicator bits (13)* 4 555 aa 2aa 55 ba+555 90 ba+x03 (13)* program 4 555 aa 2aa 55 555 a0 pa data chip erase 6 555 aa 2aa 55 555 80 555 aa 2aa 55 555 10 sector erase 6 555 aa 2aa 55 555 80 555 aa 2aa 55 sa 30 unlock bypass mode entry 3 555 aa 2aa 55 555 20 program (14, 15) 2 xx a0 pa pd sector erase (14, 15) 2 xx 80 sa 30 erase (14, 15) 2 xx 80 xxx 10 cfi (14, 15) 1 xx 98 reset (20) 2 xx 90 xxx 00 erase suspend (16) 1 ba b0 erase resume (17) 1 ba 30 set configuration register (18) 3 555 aa 2aa 55 (cr)555 c0 cfi query (19) 1 55 98
may 10, 2006 27024b3 am29bds128h/am29bds640h 47 data sheet table 21. sector protection command definitions legend: x = don?t care pa = address of the memory location to be programmed. addresses latch on the rising edge of the avd# pulse or active edge of clk which ever comes first. sa = address of the sector to be verified (in autoselect mode) or erased. address bits amax?a12 uniquely select any sector. ba = address of the bank (bds128h: a22?a20; bds640h: a21?a19) for which command is being written. sla = address of the sector to be locked. set sector address (sa) and either a6 = 1 for unlocked or a6 = 0 for locked. ow = address (a7?a0) is (00011010). pd3?pd0 = password data. pd3?pd0 present four 16 bit combinations that represent the 64-bit password. pwa = password address. address bits a1 and a0 are used to select each 16-bit portion of the 64-bit entity. pl = address (a7?a0) is (00001010) rd(0) = dq0 protection indicator bit. if protected, dq0 = 1. if unprotected, dq0 = 0. rd(1) = dq1 protection indicator bit. if protected, dq1 = 1. if unprotected, dq1 = 0. sba = sector address block to be protected. sl = address (a7?a0) is (00010010) wd= write data. see ?configuration register? definition for specific write data wp = address (a7?a0) is (00000010) wpe = address (a7?a0) is (01000010) notes: 1. see table 1 for description of bus operations. 2. all values are in hexadecimal. 3. shaded cells indicate read cycles. all others are write cycles. 4. data bits dq15?dq8 are don?t care in command sequences, except for rd, pd, wd, pwd, and pd3?pd0. 5. unless otherwise noted, address bits amax?a12 are don?t cares. 6. writing incorrect address and data values or writing them in the improper sequence may place the device in an unknown state. the system must write the reset command to return the device to reading array data. 7. no unlock or command cycles required when bank is reading array data. 8. not supported in synchronous read mode, command mode verify are always asynchronous read operations. 9. the fourth cycle programs the addressed locking bit. the fifth and sixth cycles are used to validate whether the bit has been fully programmed. if dq0 (in the sixth cycle) reads 0, the program command must be issued and verified again. 10. the fourth cycle erases all ppbs. the fifth and sixth cycles are used to validate whether the bits have been fully erased. if dq0 (in the sixth cycle) reads 1, the erase command must be issued and verified again. 11. the entire four bus-cycle sequence must be entered for each portion of the password. 12. before issuing the erase command, all ppbs should be programmed in order to prevent over-erasure of ppbs. 13. in the fourth cycle, 01h indicates ppb set; 00h indicates ppb not set. command sequence (notes) cycles bus cycles (notes 1?6) first second third fourth fifth sixth seventh addr data addr data addr data addr data addr data addr data addr data secsi sector entry 3 555 aa 2aa 55 555 88 exit 4 555 aa 2aa 55 555 90 xx 00 protection bit program (8, 9) 6 555 aa 2aa 55 555 60 sa+ow 68 sa+ow 48 ow rd(0) password program (11) 4 555 aa 2aa 55 555 38 xx[0?3] pd[0?3] verify (11) 4 555 aa 2aa 55 555 c8 xx[0?3] pd[0?3] unlock (11) 7 555 aa 2aa 55 555 28 xx0 pd0 xx1 pd1 xx2 pd2 xx3 pd3 ppb program (8, 9) 6 555 aa 2aa 55 555 60 sba+wp 68 sba+wp 48 xx rd(0) all erase (8, 10, 12) 6 555 aa 2aa 55 555 60 wpe 60 sba+ wpe 40 xx rd(0) status (13) 4 555 aa 2aa 55 ba+555 90 sba+wp rd(0) ppb lock bit set 3 555 aa 2aa 55 555 78 status (8) 4 555 aa 2aa 55 ba+555 58 sa rd(1) dyb write 4 555 aa 2aa 55 555 48 sa x1 erase 4 555 aa 2aa 55 555 48 sa x0 status 4 555 aa 2aa 55 ba+555 58 sa rd(0) password protection locking bit program (8, 9) 6 555 aa 2aa 55 555 60 pl 68 pl 48 pl rd(0) persistent protection locking bit program (8, 9) 6 555 aa 2aa 55 555 60 sl 68 sl 48 sl rd(0)
48 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet write operation status the device provides several bits to determine the status of a program or erase operation: dq2, dq3, dq5, dq6, and dq7. table 23, ?write operation status,? on page 52 and the following subsections describe the function of these bits. dq7 and dq6 each offers a method for determining whether a program or erase operation is complete or in progress. dq7: data# polling the data# polling bit, dq7, indicates to the host system whether an embedded program or erase algo- rithm is in progress or completed, or whether a bank is in erase suspend. data# pollin g is valid after the rising edge of the final we# pulse in the command sequence. during the embedded program algorithm, the device outputs on dq7 the complement of the datum pro- grammed to dq7. this dq7 status also applies to pro- gramming during erase suspend. when the embedded program algorithm is complete, the device outputs the datum programmed to dq7. the system must provide the program address to read valid status information on dq7. if a pr ogram address falls within a protected sector, data# polling on dq7 is active for approximately t psp , then that bank returns to the read mode. during the embedded erase algorithm, data# polling produces a ?0? on dq7. when the embedded erase algorithm is complete, or if the bank enters the erase suspend mode, data# polling produces a ?1? on dq7. the system must provide an address within any of the sectors selected for erasure to read valid status infor- mation on dq7. after an erase command sequence is written, if all sectors selected for erasing are protected, data# polling on dq7 is active for approximately t asp , then the bank returns to the read mode. if not all selected sectors are protected, the embedded erase algorithm erases the unprotected sectors, and ignores the selected sectors that are protected. however, if the system reads dq7 at an address within a protected sector, the status may not be valid. just prior to the completion of an embedded program or erase operation, dq7 may change asynchronously with dq6?dq0 while output enable (oe#) is asserted low. that is, the device may change from providing status information to valid data on dq7. depending on when the system samples the dq7 output, it may read the status or valid data. even if the device has com- pleted the program or erase operation and dq7 has valid data, the data outputs on dq6-dq0 may be still invalid. valid data on dq7-dq0 will appear on succes- sive read cycles. table 23, ?write operation status,? on page 52 shows the outputs for data# polling on dq7. figure 8, ?data# polling algorithm,? on page 48 shows the data# polling algorithm. figure 40, ?data# polling timings (during embedded algorithm),? on page 76 in the ac characteristics section sh ows the data# polling timing diagram. notes: 1. va = valid address for programming. during a sector erase operation, a valid address is any sector address within the sector being erased. during chip erase, a valid address is any non-pr otected sector address. 2. dq7 should be rechecked even if dq5 = ?1? because dq7 may change simultaneously with dq5. figure 8. data# polling algorithm
may 10, 2006 27024b3 am29bds128h/am29bds640h 49 data sheet rdy: ready the rdy is a dedicated output that, when the device is configured in the synchronous mode, indicates (when at logic low) the system should wait 1 clock cycle before expecting the next word of data. the rdy pin is only controlled by ce#. using the rdy configuration command sequence, rdy can be set so that a logic low indicates the system should wait 2 clock cycles before expecting valid data. the following conditions cause the rdy output to be low: during the initial access (in burst mode), and after the boundary that occurs every 64 words beginning with the 64th address, 3fh. when the device is configured in asynchronous mode, the rdy is an open-drain output pin which indicates whether an embedded algorithm is in progress or com- pleted. the rdy status is valid after the rising edge of the final we# pulse in the command sequence. if the output is low (busy), the device is actively erasing or programming. (this includes programming in the erase suspend mode.) if the output is in high imped- ance (ready), the device is in the read mode, the standby mode, or in the erase-suspend-read mode. table 23, ?write operation status,? on page 52 shows the outputs for rdy. dq6: toggle bit i toggle bit i on dq6 indicates whether an embedded program or erase algorithm is in progress or complete, or whether the device has entered the erase suspend mode. toggle bit i may be read at any address in the same bank, and is valid after the rising edge of the final we# pulse in the command sequence (prior to the program or erase operation), and during the sector erase time-out. during an embedded program or erase algorithm operation, successive read cycles to any address cause dq6 to toggle. when the operation is complete, dq6 stops toggling. after an erase command sequence is written, if all sectors selected for erasing are protected, dq6 toggles for approximately t asp , all sectors protected toggle time, then returns to reading array data. if not all selected sectors are protected, the embedded erase algorithm erases the unprotected sectors, and ignores the selected sectors that are protected. the system can use dq6 and dq2 together to deter- mine whether a sector is actively erasing or is erase-suspended. when the device is actively erasing (that is, the embedded erase algorithm is in progress), dq6 toggles. when the device enters the erase suspend mode, dq6 stops toggling. however, the system must also use dq2 to determine which sectors are erasing or erase-suspended. alternatively, the system can use dq7 (see the subsection on dq7: data# polling). if a program address falls within a protected sector, dq6 toggles for approximately t psp after the program command sequence is written, then returns to reading array data. dq6 also toggles during the erase-suspend-program mode, and stops toggling once the embedded program algorithm is complete. see the following for additional information: figure 9, ?toggle bit algorithm,? on page 50 , ?dq6: toggle bit i? on page 49 , figure 41, ?toggle bit timings (during embedded algorithm),? on page 76 (toggle bit timing diagram), and table 22, ?dq6 and dq2 indica- tions,? on page 51 . toggle bit i on dq6 requires either oe# or ce# to be deasserted and reasserted to show the change in state.
50 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet figure 9. toggle bit algorithm dq2: toggle bit ii the ?toggle bit ii? on dq2, when used with dq6, indi- cates whether a particular sector is actively erasing (that is, the embedded erase algorithm is in progress), or whether that sector is erase-suspended. toggle bit ii is valid after the rising edge of the final we# pulse in the command sequence. dq2 toggles when the system reads at addresses within those sectors that have been selected for era- sure. but dq2 cannot distinguish whether the sector is actively erasing or is erase-suspended. dq6, by com- parison, indicates whethe r the device is actively erasing, or is in erase suspend, but cannot distinguish which sectors are selected for erasure. thus, both status bits are required for sector and mode informa- tion. refer to table 22, ?dq6 and dq2 indications,? on page 51 to compare outputs for dq2 and dq6. see the following for additional information: figure 9, ?toggle bit algorithm,? on page 50, ?dq6: toggle bit i? on page 49, figure 41, ?toggle bit timings (during embedded algorithm),? on page 76 , and table 22, ?dq6 and dq2 indications,? on page 51 . start no yes yes dq5 = 1? no yes dq6 = toggle? no read byte (dq7-dq0) address = va dq6 = toggle? read byte twice (dq7-dq0) adrdess = va read byte (dq7-dq0) address = va fail pass note: the system should recheck t he toggle bit even if dq5 = ?1? because the toggle bit may stop toggling as dq5 changes to ?1.? see the subsections on dq6 and dq2 for more information.
may 10, 2006 27024b3 am29bds128h/am29bds640h 51 data sheet table 22. dq6 and dq2 indications reading toggle bits dq6/dq2 refer to figure 9, ?toggle bit algorithm,? on page 50 for the following discussion. whenever the system initially begins reading toggle bit status, it must read dq7?dq0 at least twice in a row to determine whether a toggle bit is toggling. typically, the system would note and store the value of the toggle bit after the first read. after the second read, the system would compare the new value of the toggle bit with the first. if the toggle bit is not tog- gling, the device has completed the program or erase operation. the system can read array data on dq7?dq0 on the following read cycle. however, if after the initial two read cycles, the system determines that the toggle bit is still toggling, the system also should note whether the value of dq5 is high (see the section on dq5). if it is, the system should then determine again whether the toggle bit is toggling, since the toggle bit may have stopped tog- gling just as dq5 went high. if the toggle bit is no longer toggling, the device has successfully completed the program or erase operation. if it is still toggling, the device did not completed th e operation successfully, and the system must write the reset command to return to reading array data. the remaining scenario is that the system initially determines that the toggle bit is toggling and dq5 has not gone high. the system may continue to monitor the toggle bit and dq5 through successive read cycles, determining the status as described in the previous paragraph. alternatively, it may choose to perform other system tasks. in this case, the system must start at the beginning of the algorithm when it returns to determine the status of the operation ( figure 9, ?toggle bit algorithm,? on page 50 ). dq5: exceeded ti ming limits dq5 indicates whether the program or erase time has exceeded a specified intern al pulse count limit. under these conditions dq5 produces a ?1,? indicating that the program or erase cycle was not successfully com- pleted. the device may output a ?1? on dq5 if the system tries to program a ?1? to a location that was previously pro- grammed to ?0.? only an erase operation can change a ?0? back to a ?1.? under this condition, the device halts the operation, and when the timing limit has been exceeded, dq5 produces a ?1.? under both these conditions, the system must write the reset command to return to the read mode (or to the erase-suspend-read mode if a bank was previously in the erase-suspend-program mode). dq3: sector erase timer after writing a sector erase command sequence, the system may read dq3 to determine whether or not erasure has begun. (the sector erase timer does not apply to the chip erase command.) if additional sectors are selected for erasure, the entire time-out also applies after each additional sector erase command. when the time-out period is complete, dq3 switches from a ?0? to a ?1.? if the time between additional sector erase commands from the system can be assumed to be less than t sea , the system need not monitor dq3. see also ?sector erase command sequence? on page 38 . after the sector erase command is written, the system should read the status of dq7 (data# polling) or dq6 (toggle bit i) to ensure that the device has accepted the command sequence, and then read dq3. if dq3 is ?1,? the embedded erase algorithm has begun; all further commands (except erase suspend) are ignored until the erase operation is complete. if dq3 is ?0,? the if device is and the system reads then dq6 and dq2 programming, at any address, toggles, does not toggle. actively erasing, at an address within a sector selected for erasure, toggles, also toggles. at an address within sectors not selected for erasure, toggles, does not toggle. erase suspended, at an address within a sector selected for erasure, does not toggle, toggles. at an address within sectors not selected for erasure, returns array data, returns array data. the system can read from any sector not selected for erasure. programming in erase suspend at any address, toggles, is not applicable.
52 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet device will accept additi onal sector erase commands. to ensure the command has been accepted, the system software should check the status of dq3 prior to and following each subsequent sector erase com- mand. if dq3 is high on the second status check, the last command might not have been accepted. ta b l e 2 3 shows the status of dq3 relative to the other status bits. table 23. write operation status notes: 1. dq5 switches to ?1? when an embedded program or embedde d erase operation has exceeded the maximum timing limits. refer to the section on dq5 for more information. 2. dq7 and dq2 require a valid address when reading status inform ation. refer to the appropriate subsection for further details. 3. when reading write operation status bits, the system must always provide the bank address where the embedded algorithm is in progress. the device outputs array data if the system addr esses a non-busy bank. 4. the system may read either asynchronously or synchronously (burst) while in erase suspend. 5. the rdy pin acts a dedicated output to indicate the status of an embedded erase or program operation is in progress. this is available in the asynchronous mode only. status dq7 (note 2) dq6 dq5 (note 1) dq3 dq2 (note 2) rdy (note 5) standard mode embedded program algorithm dq7# toggle 0 n/a no toggle 0 embedded erase algorithm 0 toggle 0 1 toggle 0 erase suspend mode erase-suspend- read (note 4) erase suspended sector 1 no toggle 0 n/a toggle high impedance non-erase suspended sector data data data data data high impedance erase-suspend-program dq7# toggle 0 n/a n/a 0
may 10, 2006 27024b3 am29bds128h/am29bds640h 53 data sheet absolute maximum ratings storage temperature plastic packages . . . . . . . . . . . . . . . ?65c to +150c ambient temperature with power applied. . . . . . . . . . . . . . ?65c to +125c voltage with respect to ground: all inputs and i/os except as noted below (note 1) . . . . . . . ?0.5 v to v io + 0.5 v v cc (note 1) . . . . . . . . . . . . . . . . . . ?0.5 v to +2.5 v v io . . . . . . . . . . . . . . . . . . . . . . . . . ?0.5 v to +2.5 v a9, reset#, acc (note 1) . . . . .?0.5 v to +12.5 v output short circuit current (note 3) . . . . . . 100 ma notes: 1. minimum dc voltage on input or i/os is ?0.5 v. during voltage transitions, inputs or i/os may undershoot v ss to ?2.0 v for periods of up to 20 ns. see figure 10. maximum dc voltage on input or i/os is v cc + 0.5 v. during voltage transitions outputs may overshoot to v cc + 2.0 v for periods up to 20 ns. see figure 11. 2. no more than one output may be shorted to ground at a time. duration of the short ci rcuit should not be greater than one second. 3. stresses above those listed under ?absolute maximum ratings? may cause permanent damage to the device. this is a stress rating only; functional operation of the de- vice at these or any other conditions above those indicated in the operational sections of this data sheet is not implied. exposure of the device to absolute maximum rating condi- tions for extended periods may affect device reliability. figure 10. maximum negative overshoot waveform figure 11. maximum positive overshoot waveform operating ranges industrial (i) devices ambient temperature (t a ) . . . . . . . . . ?40c to +85c supply voltages v cc supply voltages . . . . . . . . . . .+1.65 v to +1.95 v . . . . . . . . . . . . . . . . . . . . . . . . . . . v cc v io ?100 mv v io supply voltages . . . . . . . . . . . +1.65 v to +1.95 v operating ranges define those li mits between which the func- tionality of the device is guaranteed. 20 ns 20 ns +0.8 v ?0.5 v 20 ns ?2.0 v 20 ns 20 ns v cc +2.0 v v cc +0.5 v 20 ns 1.0 v
54 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet dc characteristics cmos compatible note: 1. maximum i cc specifications are tested with v cc = v cc max. 2. v io = v cc 3. the i cc current listed is typically le ss than 2 ma/mhz, with oe# at v ih . 4. i cc active while embedded erase or embedded program is in progress. 5. device enters automatic sleep mode when addresses are stable for t acc + 60 ns. typical sleep mode current is equal to i cc3 . 6. total current during accelerated programming is the sum of v acc and v cc currents. parameter description test conditions note: 1 & 2 min typ max unit i li input load current v in = v ss to v cc , v cc = v cc max 1 a i lo output leakage current v out = v ss to v cc , v cc = v cc max 1 a i ccb v cc active burst read current ce# = v il , oe# = v ih , we# = v ih , burst length = 8 54 mhz 9 17 ma ce# = v il , oe# = v ih , we# = v ih , burst length = 16 54 mhz 8 15.5 ma ce# = v il , oe# = v ih , we# = v ih , burst length = continuous 54 mhz 7 14 ma i io1 v io non-active output oe# = v ih 140a i cc1 v cc active asynchronous read current (note 3) ce# = v il , oe# = v ih , we# = v ih 10 mhz 20 30 ma 5 mhz 10 15 ma 1 mhz 3.55ma i cc2 v cc active write current (note 4) ce# = v il , oe# = v ih , acc = v ih 15 40 ma i cc3 v cc standby current (note 5) ce# = reset# = v cc 0.2 v 0.2 40 a i cc4 v cc reset current reset# = v il, clk = v il 140a i cc5 v cc active current (read while write) ce# = v il , oe# = v ih 25 60 ma i cc6 v cc sleep current ce# = v il , oe# = v ih 140a i acc accelerated program current (note 6) ce# = v il , oe# = v ih, v acc = 12.0 0.5 v v acc 715ma v cc 510ma v il input low voltage v io = 1.8 v ?0.4 0.4 v v ih input high voltage v io = 1.8 v v io ? 0.4 v io + 0.4 v v ol output low voltage i ol = 100 a, v io = v cc = v cc min 0.1 v v oh output high voltage i oh = ?100 a, v io = v cc = v cc min v io ? 0.1 v v id voltage for autoselect and temporary sector unprotect v cc = 1.8 v 11.5 12.5 v v hh voltage for accelerated program 11.5 12.5 v v lko low v cc lock-out voltage 1.0 1.4 v
may 10, 2006 27024b3 am29bds128h/am29bds640h 55 data sheet test conditions table 24. test specifications key to switching waveforms switching waveforms c l device under te s t figure 12. test setup test condition all speed options unit output load capacitance, c l (including jig capacitance) 30 pf input rise and fall times 3 ns input pulse levels 0.0?v io v input timing measurement reference levels v io /2 v output timing measurement reference levels v io /2 v waveform inputs outputs steady changing from h to l changing from l to h don?t care, any change permitted changing, state unknown does not apply center line is high impedance state (high z) figure 13. input waveforms and measurement levels v io 0.0 v output measurement level input v io /2 v io /2 all inputs and outputs
56 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet ac characteristics v cc power-up figure 14. v cc power-up diagram notes: 1. v cc v io ?100 mv and v cc ramp rate exceeds 1 v/100 s . 2. if the v cc ramp rate is less than 1 v /100 s, a hardware reset will be required. clk characterization figure 15. clk characterization parameter description test setup speed unit t vcs v cc setup time min 50 s t vios v io setup time min 50 s t rsth reset# low hold time min 50 s parameter description 66 mhz 54 mhz unit f clk clk frequency max 66 54 mhz t clk clk period min 15 18.5 ns t ch clk high time min 6.0 7.4 ns t cl clk low time t cr clk rise time max 3 3 ns t cf clk fall time v cc f v io f reset# t vcs t rsth t vios t clk t cl t ch t cr t cf clk
may 10, 2006 27024b3 am29bds128h/am29bds640h 57 data sheet ac characteristics synchronous/burst read note: addresses are latched on the first of either the active edge of clk or the rising edge of avd#. parameter description 66 mhz 54 mhz unit jedec standard t iacc latency (even address in reduced wait-state handshaking mode) max 56 69 ns t iacc latency (standard handshaking or odd address in reduced wait-state handshaking mode max 71 87.5 ns t bacc burst access time vali d clock to output delay max 11 13.5 ns t acs address setup time to clk (note ) min 4 5 ns t ach address hold time from clk (note ) min 6 7 ns t bdh data hold time from next clock cycle min 3 4 ns t cr chip enable to rdy valid max 11 13.5 ns t oe output enable to output valid max 11 13.5 ns t cez chip enable to high z max 8 10 ns t oez output enable to high z max 8 10 ns t ces ce# setup time to clk min 4 5 ns t rdys rdy setup time to clk min 4 5 ns t racc ready access time from clk max 11 13.5 ns t aas address setup time to avd# (note ) min 4 5 ns t aah address hold time to avd# (note ) min 6 7 ns t cas ce# setup time to avd# min 0 ns t avc avd# low to clk min 4 5 ns t avd avd# pulse min 10 12 ns t acc access time max 50 55 ns t cka clk to access resume max 11 13.5 ns t ckz clk to high z max 8 10 ns t oes output enable setup time min 4 5 ns t rcc read cycle for continuous suspend max 1 ms
58 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet ac characteristics notes: 1. figure shows total number of wait states set to seven cycles. the total number of wait states can be programmed from two cycles to seven cycles. 2. if any burst address occurs at a 64-word boundary, two additional clock cycle are inserted, and is indicated by rdy. 3. the device is in synchronous mode. figure 16. clk synchronous burst mode read (rising active clk) notes: 1. figure shows total number of wait states set to four cycles . the total number of wait states can be programmed from two cycles to seven cycles. clock is set for active falling edge. 2. if any burst address occurs at a 64-word boundary, two additional clock cycle are inserted, and is indicated by rdy. 3. the device is in synchronous mode. figure 17. clk synchronous burst mode read (falling active clock) da da + 1 da + n oe# data addresses aa avd# rdy clk ce#f t ces t acs t avc t avd t ach t oe t racc t oez t cez t iacc t acc t bdh 7 cycles for initial access shown. hi-z hi-z hi-z 1 2 34 56 7 t rdys t bacc t cr da da + 1 da + n oe# data addresses aa avd# rdy clk ce# t ces t acs t avc t avd t ach t oe t oez t cez t iacc t acc t bdh 4 cycles for initial access shown. t racc hi-z hi-z hi-z 12345 t rdys t bacc t cr
may 10, 2006 27024b3 am29bds128h/am29bds640h 59 data sheet ac characteristics notes: 1. figure shows total number of wait states set to seven cycles. the total number of wait states can be programmed from two cycles to seven cycles. clock is set for active rising edge. 2. if any burst address occurs at a 64-word boundary, two additional clock cycle are inserted, and is indicated by rdy. 3. the device is in synchronous mode. figure 18. synchronous burst mode read note: figure assumes 7 wait states for initial access and automati c detect synchronous read. d0?d7 in data waveform indicate the order of data within a given 8-word address range, from lo west to highest. starting address in figure is the 7th address in range (a6). see ?requirements for synchronous (burst) read operation?. the set configurat ion register command sequence has been written with a18=1; device will output rdy with valid data. figure 19. 8-word linear burst with wrap around da da + 1 da + n oe# data addresses aa avd# rdy clk ce# t cas t aas t avc t avd t aah t oe t racc t oez t cez t iacc t bdh 7 cycles for initial access shown. hi-z hi-z hi-z 1234567 t rdys t bacc t acc t cr d6 d7 oe# data addresses a6 avd# rdy clk ce# t ces t acs t avc t avd t ach t oe t iacc t bdh d0 d1 d5 d6 7 cycles for initial access shown. hi-z t racc 1 234567 t rdys t bacc t acc t cr
60 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet ac characteristics note: figure assumes 6 wait states for initial access and synchrono us read. the set configuratio n register command sequence has been written with a18=0; device will output rdy o ne cycle before valid data. figure 20. linear burst with rdy set one cycle before data da+1 da da+2 da+3 da + n oe# data addresses aa avd# rdy clk ce# t ces t acs t avc t avd t ach t oe t racc t oez t cez t iacc t bdh 6 wait cycles for initial access shown. hi-z hi-z hi-z 1 23456 t rdys t bacc t acc t cr
may 10, 2006 27024b3 am29bds128h/am29bds640h 61 data sheet ac characteristics note: figure is for any even address other than 3eh (or multiple thereof). figure 21. reduced wait-state handshake burst suspend/resume at an even address note: figure is for any odd address ot her than 3fh (or multiple thereof). figure 22. reduced wait-state handshake burst suspend/resume at an odd address d(23) d(24) d(23) d(20) d(21) d(22) d(23) addresses avd# data rdy d(20) t oes t oes t cka t ckz x+1 x+2 x+3 x+4 x+5 x+6 x x+7 x+8 oe# t racc suspend resume clk t racc d(25) d(27) d(26) d(23) d(24) d(25) d(25) addresses avd# data rdy d(23) t oes t oes t cka t ckz x+1 x+2 x+3 x+4 x+5 x+6 x x+7 x+8 oe# t racc suspend resume clk t racc
62 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet ac characteristics figure 23. reduced wait-state handshake burst suspend/resume at address 3eh (or offset from 3eh) figure 24. reduced wait-state handshake burst suspend/resume at address 3fh (or offset from 3fh by a multiple of 64) addresses avd# data rdy d(3e) t oes t oes t cka t ckz oe# d(40) d(3f) d(3f) d(3f) suspend resume d(41) d(41) d(41) clk x x+1 x+2 x+3 x+4 x+5 x+6 x+7 x+8 x+9 x+10 t racc d(3e) d(42) d(41) t racc addresses avd# data rdy d(3f) t oes t oes t cka t ckz oe# d(41) d(3f) d(3f) d(40) suspend resume d(41) d(41) d(41) t racc clk x x+1 x+2 x+3 x+4 x+5 x+6 x+7 x+8 x+9 x+10 d(3f) d(43) d(42) t racc t racc
may 10, 2006 27024b3 am29bds128h/am29bds640h 63 data sheet ac characteristics note: figure assumes 6 wait states for initial access and synchrono us read. the set configuratio n register command sequence has been written with a18=0; device will output rdy with valid data. 1) rdy goes low during the two-cycl e latency during a boundary crossing. 2) rdy stays high when a burst sequence crosses no boundaries. figure 25. standard handshake burst suspend prior to initial access note: figure assumes 6 wait states for initial access and synchrono us read. the set configuratio n register command sequence has been written with a18=0; device will output rdy with valid data. 1) burst suspend during the initial synchronous access 2) burst suspend after one clock cycle following the initial synchronous access figure 26. standard handshake burst suspend at or after initial access addresses a(n) avd# data(2) rdy(2) rdy(1) t oes t oes t cka t racc t racc 1 234 5 6 7 x+1 x+2 x+3 x+4 x+5 x+6 x x+7 x+8 oe# data(1) t acc d(40) d(3f) d(n) d(n+1) d(n+2) 3f 3f clk d(n) d(n+1) d(n+2) d(n+3) d(n+4) d(n+5) d(n+6) suspend resume addresses a(n) avd# oe#(1) data(1) data(2) oe#(2) rdy(1) d(n) d(n+1) suspend resume t acc t racc t oes t cka d(n) t oes 1 234 5 6 7 8 9 x x+1 x+2 x+3 clk t racc t oes t racc t cka d(n+1) d(n+2) d(n) d(n+1) t racc t racc t racc t ckz rdy(2)
64 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet ac characteristics note: figure assumes 6 wait states for initial access and synchrono us read. the set configuratio n register command sequence has been written with a18=0; device will output rdy with valid data. figure 27. standard handshake burst suspend at address 3fh (starting address 3dh or earlier) note: figure assumes 6 wait states for initial access and synchrono us read. the set configuratio n register command sequence has been written with a18=0; device will output rdy with valid data. 1) address is 3eh or offset by a multiple of 64 (40h). 2) address is 3fh or offset by a multiple of 64 (40h). figure 28. standard handshake burst suspend at address 3eh/3fh (without a valid initial access) addresses a(3d) avd# oe# data rdy d(3f) d(3f) d(3f) d(4d) suspend resume t acc t racc t oes t oes t cka t cka d(3d) t racc 1 234 5 6 7 8 9 x x+1 x+2 x+3 x+4 x+5 clk t racc d(3e) d(3f) t oes t ckz addresses(1) a(3e) avd# clk 1 23 4 5 67 x+1 x+2 x+3 x+4 x+5 x+6 x oe# data(1) addresses(2) data(2) rdy(2) rdy(1) d(3e) d(3f) d(41) d(40) d(42) suspend resume t oes t acc t racc t ckz t oes t oes t cka a(3f) 8 d(3f) t racc t racc t racc t racc t racc d(40) d(42) d(41) d(43) d(3e) d(3f)
may 10, 2006 27024b3 am29bds128h/am29bds640h 65 data sheet ac characteristics note: figure assumes 6 wait states for initial access and synchrono us read. the set configuratio n register command sequence has been written with a18=0; device will output rdy with valid data. 1) address is 3eh or offset by a multiple of 64 (40h) 2) address is 3fh or offset by a multiple of 64 (40h) figure 29. standard handshake burst suspend at address 3eh/3fh (with 1 access clk) note: figure assumes 6 wait states for initial access and synchrono us read. the set configuratio n register command sequence has been written with a18=0; device will output rdy with valid data. 1) device crosses a page boundary prior to t rcc . 2) device neither crosses a page boundary nor latches a new address prior to t rcc . figure 30. read cycle for continuous suspend addresses(1) a(3e) avd# clk 1 23 4 5 67 x+1 x+2 x+3 x+4 x+5 x+6 x oe# data(1) addresses(2) data(2) rdy(2) (odd) rdy(1) (even) d(3e) d(3f) d(41) d(40) d(42) d(40) d(42) d(41) d(43) suspend resume t oes t acc t racc t ckz t oes t oes t cka a(3f) 8 d(3f) d(3f) 9 t racc d(40) t racc t racc t racc t racc addresses a(n) avd# data(2) ce# rdy d(n) ??? t oes t oes t cka t racc t rcc t rcc ??? 1 234 5 6 7 x+1 x+2 x+3 x+4 x+5 x+6 x x+7 x+8 oe# data(1) t acc d(40) d(3f) d(n) d(n+1) d(n+2) d(3f) d(3f) clk suspend resume
66 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet ac characteristics asynchronous mode read notes: 1. asynchronous access time is from the last of ei ther stable addresses or the falling edge of avd#. 2. not 100% tested. parameter description 75 mhz 66 mhz 54 mhz unit jedec standard t ce access time from ce# low max 45 50 55 ns t acc asynchronous access time (note 1) max 45 50 55 ns t avdp avd# low time min 10 12 ns t aavds address setup time to rising edge of avd min 4 5 ns t aavdh address hold time from rising edge of avd min 5.5 6 7 ns t oe output enable to output valid max 8.5 11 13.5 ns t oeh output enable hold time read min 0 ns toggle and data# polling min 8 10 ns t oez output enable to high z (note 2) max 8 10 ns t cas ce# setup time to avd# min 0 ns
may 10, 2006 27024b3 am29bds128h/am29bds640h 67 data sheet ac characteristics note: ra = read address, rd = read data. figure 31. asynchronous mode read with latched addresses note: ra = read address, rd = read data. figure 32. asynchronous mode read t ce we# addresses ce# oe# valid rd t acc t oeh t oe data t oez t aavdh t avdp t aavds avd# ra t cas t ce we# addresses ce# oe# valid rd t acc t oeh t oe data t oez avd# ra
68 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet ac characteristics hardware reset (reset#) note: not 100% tested. parameter description all speed options unit jedec std t readyw reset# pin low (during embedded algorithms) to read mode (see note) max 20 s t ready reset# pin low (not during embedded algorithms) to read mode (see note) max 500 ns t rp reset# pulse width min 500 ns t rh reset high time before read (see note) min 200 ns t rpd reset# low to standby mode min 20 s reset# t rp t ready reset timings not during embedded algorithms t readyw ce#, oe# t rh ce#, oe# reset timings during embedded algorithms reset# t rp figure 33. reset timings
may 10, 2006 27024b3 am29bds128h/am29bds640h 69 data sheet ac characteristics erase/program operations notes: 1. not 100% tested. 2. asynchronous mode allows both asynchronous and synchronous program operation. synchronous mode allows both asynchronous and synchronous program operation. 3. in asynchronous program operation timing, addresses are latched on the falling edge of we# or rising edge of avd#. in synchronous program operation timing, addresses are latched on the first of either the falling edge of we# or the active edge of clk. 4. see the ?erase and programming performance? section for more information. 5. does not include the preprogramming time. parameter description 75 mhz 66 mhz 54 mhz unit jedec standard t avav t wc write cycle time (note 1) min 45 50 55 ns t avwl t as address setup time (notes 2, 3) synchronous min 45 ns asynchronous 0 t wlax t ah address hold time (notes 2, 3) synchronous min 5.5 6 7 ns asynchronous 15 20 20 t avdp avd# low time min 10 12 ns t dvwh t ds data setup time min 20 45 ns t whdx t dh data hold time min 0 ns t ghwl t ghwl read recovery time before write min 0 ns t cas ce# setup time to avd# min 0 ns t wheh t ch ce# hold time min 0 ns t wlwh t wp write pulse width min 20 30 ns t whwl t wph write pulse width high min 15 20 20 ns t sr/w latency between read and write operations min 0 ns t vid v acc rise and fall time min 500 ns t vids v acc setup time (during accelerated programming) min 1 s t vcs v cc setup time min 50 s t elwl t cs ce# setup time to we# min 0 ns t avsw avd# setup time to we# min 4 5 ns t avhw avd# hold time to we# min 4 5 ns t acs address setup time to clk (notes 2, 3) min 4 5 ns t ach address hold time to clk (notes 2, 3) min 5.5 6 7 ns t avhc avd# hold time to clk min 4 5 ns t csw clock setup time to we# min 5 ns t sea sector erase accept timeout max 50 s t esl erase suspend latency max 35 s t asp toggle time during sector protection typ 100 s t psp toggle time during programming within a protected sector ty p 1 s
70 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet ac characteristics notes: 1. pa = program address, pd = program data, va = valid address for reading status bits. 2. ?in progress? and ?complete? refe r to status of program operation. 3. amax?a12 are don?t care during command sequence unlock cycles. 4. clk can be either v il or v ih . 5. the asynchronous programming operation is independent of the set device read mode bit in the configuration register. figure 34. asynchronous program operation timings: avd# latched addresses oe# ce#f data addresses avd# we# clk v cc f t as t wp t ah t wc t wph pa t vcs t cs t dh t ch in progress t whwh1 va complete va program command sequence (last two cycles) read status data t ds v ih v il t avdp a0h 555h pd
may 10, 2006 27024b3 am29bds128h/am29bds640h 71 data sheet ac characteristics notes: 1. pa = program address, pd = program data, va = valid address for reading status bits. 2. ?in progress? and ?complete? refe r to status of program operation. 3. amax?a12 are don?t care during command sequence unlock cycles. 4. clk can be either v il or v ih . 5. the asynchronous programming operation is independent of the set device read mode bit in the configuration register. figure 35. asynchronous program operation timings: we# latched addresses oe# ce#f data addresses avd# we# clk v cc f 555h pd t as t avsw t avhw t ah t wc t wph pa t vcs t wp t dh t ch in progress t whwh1 va complete va program command sequence (last two cycles) read status data t ds v ih v il t avdp a0h t cs
72 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet ac characteristics notes: 1. pa = program address, pd = program data, va = valid address for reading status bits. 2. ?in progress? and ?complete? refe r to status of program operation. 3. amax?a12 are don?t care during command sequence unlock cycles. 4. addresses are latched on the firs t of either the rising edge of avd# or the active edge of clk. 5. either ce# or avd# is required to go from lo w to high in between programming command sequences. 6. the synchronous programming operation is dependent of the set device read mode bit in the configuration register. the configuration register must be set to the synchronous read mode. figure 36. synchronous program operation timings: we# latched addresses oe# ce#f data addresses avd# we# clk v cc f 555h pd t wc t wph t wp pa t vcs t dh t ch in progress t whwh1 va complete va program command sequence (last two cycles) read status data t ds t avdp a0h t acs t cas t ach t avch t csw
may 10, 2006 27024b3 am29bds128h/am29bds640h 73 data sheet ac characteristics notes: 1. pa = program address, pd = program data, va = valid address for reading status bits. 2. ?in progress? and ?complete? refe r to status of program operation. 3. amax?a12 are don?t care during command sequence unlock cycles. 4. addresses are latched on the firs t of either the rising edge of avd# or the active edge of clk. 5. either ce# or avd# is required to go from lo w to high in between programming command sequences. 6. the synchronous programming operation is dependent of the set device read mode bit in the configuration register. the configuration register must be set to the synchronous read mode. figure 37. synchronous program operation timings: clk latched addresses oe# ce#f data addresses avd# we# clk v cc f 555h pd t wc t wph t wp pa t vcs t dh t ch in progress t whwh1 va complete va program command sequence (last two cycles) read status data t ds t avdp a0h t as t cas t ah t avch t csw
74 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet ac characteristics figure 38. chip/sector erase command sequence notes: 1. sa is the sector address for sector erase. 2. address bits amax?a12 are don?t cares during unlock cycles in the command sequence. oe# ce# data addresses avd# we# clk v cc t as t wp t ah t wc t wph sa t vcs t cs t dh t ch in progress t whwh2 va complete va erase command sequence (last two cycles) read status data t ds 10h for chip erase 555h for chip erase v ih v il t avdp 55h 2aah 30h
may 10, 2006 27024b3 am29bds128h/am29bds640h 75 data sheet ac characteristics note: use setup and hold times from conventional program operation. figure 39. accelerated programming timing ce# avd# we# addresses data oe# acc don't care don't care a0h don't care pa pd v id 1 s v il or v ih t vid t vids
76 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet ac characteristics notes: 1. status reads in figure are shown as asynchronous. 2. va = valid address. two read cycles are required to determi ne status. when the embedded algorithm operation is complete, and data# polling will output true data. 3. while in asynchronous mode, rdy will be low while the device is in embedded erase or programming mode. figure 40. data# polling timings (during embedded algorithm) notes: 1. status reads in figure are shown as asynchronous. 2. va = valid address. two read cycles are required to determi ne status. when the embedded algorithm operation is complete, the toggle bits will stop toggling. 3. while in asynchronous mode, rdy will be low while the device is in embedded erase or programming mode. figure 41. toggle bit timings (during embedded algorithm) we# ce# oe# t oe addresses avd# t oeh t ce t ch t oez t cez status data status data t acc va va data we# ce# oe# t oe addresses avd# t oeh t ce t ch t oez t cez status data status data t acc va va data
may 10, 2006 27024b3 am29bds128h/am29bds640h 77 data sheet ac characteristics notes: 1. the timings are similar to synchronous read timings. 2. va = valid address. two read cycles are required to determi ne status. when the embedded algorithm operation is complete, the toggle bits will stop toggling. 3. rdy is active with data (a18 = 0 in the configuration register). when a18 = 1 in the configuration register, rdy is active on e clock cycle before data. figure 42. synchronous data pol ling timings/toggle bit timings ce# clk avd# addresses oe# data rdy status data status data va va t iacc t iacc note: dq2 toggles only when read at an addre ss within an erase-suspended se ctor. the system may use oe# or ce# to toggle dq2 and dq6. figure 43. dq2 vs. dq6 enter erase erase erase enter erase suspend program erase suspend read erase suspend read erase we# dq6 dq2 erase complete erase suspend suspend program resume embedded erasing
78 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet ac characteristics temporary sector unprotect note: not 100% tested. parameter all speed options jedec std description unit t vidr v id rise and fall time (see note) min 500 ns t vhh v hh rise and fall time (see note) min 250 ns t rsp reset# setup time fo r temporary sector unprotect min 4 s t rrb reset# hold time from rdy high for temporary sector unprotect min 4 s reset# t vidr v id v il or v ih v id v il or v ih ce# we# rdy t vidr t rsp program or erase command sequence t rrb figure 44. temporary sector unprotect timing diagram
may 10, 2006 27024b3 am29bds128h/am29bds640h 79 data sheet ac characteristics sector protect: 150 s sector unprot ect: 15 ms 1 s reset# sa, a6, a1, a0 data ce# we# oe# 60h 60h 40h valid* valid* valid* status sector protect/unprotect verify v id v ih * for sector protect, a6 = 0, a1 = 1, a0 = 0. for sector unprotect, a6 = 1, a1 = 1, a0 = 0. figure 45. sector/sector block protect and unprotect timing diagram
80 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet ac characteristics) notes: 1. rdy active with data (a18 = 0 in the configuration register). 2. rdy active one clock cycle before data (a18 = 1 in the configuration register). 3. cxx indicates the clock that triggers dxx on the outputs; for example, c60 triggers d60. figure shows the device not crossing a bank in the process of performing an erase or program. 4. if the starting ad dress latched in is either 3eh or 3fh (or some 64 mult iple of either), there is no additional 2 cycle laten cy at the boundary crossing. figure 46. latency with boundary crossing clk address (hex) c60 c61 c62 c63 c63 c63 c64 c65 c66 c67 d60 d61 d62 d63 d64 d65 d66 d67 (stays high) avd# rdy(1) data address boundary occurs every 64 words, beginning at address 00003fh: 00007fh, 0000bfh, etc.) address 000000h is also a boundary crossing. 3c 3d 3e 3f 3f 3f 40 41 42 43 latency rdy(2) latency t racc t racc t racc t racc
may 10, 2006 27024b3 am29bds128h/am29bds640h 81 data sheet ac characteristics notes: 1. rdy active with data (a18 = 0 in the configuration register). 2. rdy active one clock cycle before data (a18 = 1 in the configuration register). 3. cxx indicates the clock that triggers dxx on the outputs; for example, c60 triggers d60. figure shows the device crossing a bank in the process of performing an erase or program. figure 47. latency with boundary crossing into program/erase bank clk address (hex) c60 c61 c62 c63 c63 c63 c64 d60 d61 d62 d63 read status (stays high) avd# rdy(1) data oe#, ce# (stays low) address boundary occurs every 64 words, beginning at address 00003fh: (00007fh, 0000bfh, etc.) address 000000h is also a boundary crossing. 3c 3d 3e 3f 3f 3f 40 latency rdy(2) latency t racc t racc t racc t racc invalid
82 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet ac characteristics wait state decoding addresses: a14, a13, a12 = ?111? ? reserved a14, a13, a12 = ?110? ? reserved a14, a13, a12 = ?101? ? 5 programmed, 7 total a14, a13, a12 = ?100? ? 4 programmed, 6 total a14, a13, a12 = ?011? ? 3 programmed, 5 total a14, a13, a12 = ?010? ? 2 programmed, 4 total a14, a13, a12 = ?001? ? 1 programmed, 3 total a14, a13, a12 = ?000? ? 0 programmed, 2 total note: figure assumes address d0 is not at an address boundary, ac tive clock edge is rising, and wait state is set to ?101?. figure 48. example of wait states insertion data avd# oe# clk 12345 d0 d1 01 6 2 7 3 total number of clock cycles following avd# falling edge rising edge of next clock cycle following last wait state triggers next burst data number of clock cycles p ro g rammed 45
may 10, 2006 27024b3 am29bds128h/am29bds640h 83 data sheet ac characteristics note: breakpoints in waveforms indicate that system may alternatel y read array data from the ?non-busy bank? while checking the status of the program or erase operat ion in the ?busy? bank. the system should re ad status twice to ensure valid informatio n. figure 49. back-to-back read/write cycle timings oe# ce# we# t oeh data addresses avd# pd/30h aah ra pa/sa t wc t ds t dh t rc t rc t oe t as t ah t acc t oeh t wp t ghwl t oez t wc t sr/w last cycle in program or sector erase command sequence read status (at least two cycles) in same bank and/or array data from other bank begin another write or program command sequence rd ra 555h rd t wph
84 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet erase and programming performance notes: 1. typical program and erase times assume the following conditions: 25 c, 1.8 v v cc , 1 million cycles. additionally, programming typicals assumes a checkerboard pattern. 2. under worst case conditions of 90c, v cc = 1.65 v, 1,000,000 cycles. 3. the typical chip programming time is considerably less than the maximum chip programming time listed. 4. in the pre-programming step of the embedded erase algorithm, all words are programmed to 00h before erasure. 5. system-level overhead is the time required to execute the two- or four-bus-cycle sequence for the program command. see table 20, ?memory array command definitions,? on page 46 for further information on command definitions. 6. the device has a minimum erase and pr ogram cycle endurance of 1 million cycles. bga ball capacitance notes: 1. sampled, not 100% tested. 2. test conditions t a = 25c, f = 1.0 mhz. data retention parameter typ (note 1) max (note 2) unit comments sector erase time 32 kword 0.4 5 s excludes 00h programming prior to erasure (note 4) 4 kword 0.2 5 chip erase time 128 mb 103 s 64 mb 54 s word programming time 9 210 s excludes system level overhead (note 5) accelerated word programming time 4 120 s chip programming time (note 3) 128 mb 75.5 226.5 s 64 mb 38 114 s excludes system level overhead (note 5) accelerated chip programming time 128 mb 33 99 s 64 mb 17 30 s parameter symbol parameter description test setup typ max unit c in input capacitance v in = 0 4.2 5.0 pf c out output capacitance v out = 0 5.4 6.5 pf c in2 control pin capacitance v in = 0 3.9 4.7 pf parameter test conditions min unit minimum pattern data retention time 150 c10 years 125 c20 years
may 10, 2006 27024b3 am29bds128h/am29bds640h 85 data sheet physical dimensions vbb080?80-ball fine-pitch ball grid array (bga) 11.5 x 9 mm package note: bsc is an ansi standard for basic space centering 3233 \ 16-038.9h notes: 1. dimensioning and tolerancing per asme y14.5m-1994. 2. all dimensions are in millimeters. 3. ball position designation per jesd 95-1, spp-010 (except as noted). 4. e represents the solder ball grid pitch. 5. symbol "md" is the ball row matrix size in the "d" direction. symbol "me" is the ball column matrix size in the "e" direction. n is the total number of solder balls. 6 dimension "b" is measured at the maximum ball diameter in a plane parallel to datum c. 7 sd and se are measured with respect to datums a and b and define the position of the center solder ball in the outer row. when there is an odd number of solder balls in the outer row parallel to the d or e dimension, respectively, sd or se = 0.000. when there is an even number of solder balls in the outer row, sd or se = e/2 8. not used. 9. "+" indicates the theoretical center of depopulated balls. 10 a1 corner to be identified by chamfer, laser or ink mark, metallized mark indentation or other means. package vbb 080 jedec n/a 11.50 mm x 9.00 mm nom package symbol min nom max note a --- --- 1.00 overall thickness a1 0.20 --- --- ball height a2 0.62 --- 0.76 body thickness d 11.50 bsc. body size e 9.00 bsc. body size d1 8.80 bsc. ball footprint e1 5.60 bsc. ball footprint md 12 row matrix size d direction me 8 row matrix size e direction n 80 total ball count b 0.30 0.35 0.40 ball diameter e 0.80 bsc. ball pitch sd / se 0.40 bsc. solder ball placement (a3-a6, b3-b6, l3-l6, -m3-m6) depopulated solder balls bottom view top view side view a1 corner a2 a index mark corner 10 pin a1 ml j k e c 0.05 (2x) (2x) c 0.05 a1 e d 7 ba c ed f hg 8 7 6 5 4 3 2 1 e d1 e1 se 7 b ca c m 0.15 0.08 m 6 0.10 c c 0.08 nx b sd a b c seating plane
86 am29bds128h/am29bds640h 27024b3 may 10, 2006 data sheet physical dimensions vbd064?64-ball fine-pitch ball grid array (bga) 9 x 8 mm package note: bsc is an ansi standard for basic space centering 3246 \ 16-038.9 package vbd 064 jedec n/a 8.95 mm x 7.95 mm nom package symbol min nom max note a --- --- 1.00 overall thickness a1 0.20 --- 0.30 ball height a2 0.62 --- 0.76 body thickness d 8.95 bsc. body size e 7.95 bsc. body size d1 5.60 bsc. ball footprint e1 5.60 bsc. ball footprint md 8 row matrix size d direction me 8 row matrix size e direction n 64 total ball count b 0.30 0.35 0.40 ball diameter e 0.80 bsc. ball pitch sd / se 0.40 bsc. solder ball placement none depopulated solder balls notes: 1. dimensioning and tolerancing per asme y14.5m-1994. 2. all dimensions are in millimeters. 3. ball position designation per jesd 95-1, spp-010 (except as noted). 4. e represents the solder ball grid pitch. 5. symbol "md" is the ball row matrix size in the "d" direction. symbol "me" is the ball column matrix size in the "e" direction. n is the total number of solder balls. 6 dimension "b" is measured at the maximum ball diameter in a plane parallel to datum c. 7 sd and se are measured with respect to datums a and b and define the position of the center solder ball in the outer row. when there is an odd number of solder balls in the outer row parallel to the d or e dimension, respectively, sd or se = 0.000. when there is an even number of solder balls in the outer row, sd or se = e/2 8. not used. 9. "+" indicates the theoretical center of depopulated balls. 10 a1 corner to be identified by chamfer, laser or ink mark, metallized mark indentation or other means. side view a2 a seating plane c c c 0.10 0.08 a1 top view 10 c (2x) 0.05 (2x) c 0.05 a b index mark corner pin a1 e d bottom view a1 corner sd se 7 e1 e d1 ab nx b m 0.15 0.08 m c c 6 g h 8 6 5 4 3 2 1 b a 7 d c e f
may 10, 2006 27024b3 am29bds128h/am29bds640h 87 data sheet revision summary revision a (november 5, 2002) initial release. revision b (febr uary 2, 2004) global incorporated am29bds640h specifications from pub- lication 27241. removed 1.5 v v io option. changed 80 mhz speed grade to 75 mhz. in-system sector protection/sector unprotection algorithms changed ?wait 15 ms? to ?wait 1.5 ms.? password protection mode locking bit; persistent sector protection mode locking bit program command; secsi sector protection bit program command; ppb program command; all ppb erase command updated description for these sections. command definitions changed wp to (01000010). set configuration reg- ister command is not availa ble in unlock bypass mode removed password protection locking bit read command and persistent protection locking bit read command. updated ppb progra m, erase, status com- mands to require sector block address (sba). dc characteristics updated i io1 , i cc1 , i cc3 , i cc4 , i cc6 test conditions updated input rise and fall times. v cc power up added ramp rate information. clk characterization added section. revision b+1 (august 10, 2004) global incorporated am29bds640h specifications from pub- lication 27241. updated speed options offered. revision b2 (sept ember 30, 2005) ordering information added package type vf (p b-free package (vbb080)) revision b3 (may 10, 2006) added migration and obsolescence information for am29bds640h. removed preliminary designation from document. colophon the products described in this document are designed, developed and manufactured as contemplated for general use, including wit hout limita- tion, ordinary industrial use, general o ffice use, personal use, and household use, but are not designed, developed and manufac tured as con- templated (1) for any use that includes fatal risks or dangers th at, unless extremely high safety is secured, could have a seri ous effect to the public, and could lead directly to death, personal injury, severe physical damage or other loss (i.e., nuclear reaction control in nuclear facility, aircraft flight control, air traffic contro l, mass transport control, medical life support system, missile launch control in we apon system), or (2) for any use where chance of failure is intole rable (i.e., submersible repeater and artifi cial satellite). please note that spansion will not be liable to you and/or any third party for any claims or damages arising in connection with abo ve-mentioned uses of the products. any semic onductor de- vices have an inherent chance of failure. y ou must protect against injury, damage or loss from such failures by incorporating s afety design mea- sures into your facility and equipment such as redundancy, fire protection, and prevention of ov er-current levels and other abn ormal operating conditions. if any products described in this document represent goods or technologies subject to certain restrictions on expor t under the foreign exchange and foreign trade law of japan, the us export administra tion regulations or the applicable laws of any other country, the prior au- thorization by the respective government entit y will be required for export of those products. trademarks copyright ? 2002?2006 advanced micro devices, inc. all rights reserved. amd, the amd logo, and combinations thereof are regi stered trademarks of advanced micro devices, inc. product names used in this publication are for identification purposes only and may be trademarks of their respective companies .

▲Up To Search▲

Price & Availability of AM29BDS640HD9VMI

	To Download AM29BDS640HD9VMI Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .